You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to ensure a known version of build-harness is run by various automation workflows, and to support development and testing of build-harness, if you have the build-harness project checked out from GitHub and it is in the same directory tree at the same or higher level than your project, the checked out version will be used instead of the latest version.
This leads to problems and confusion by end users when they have a checked out version and it is old.
Feature Request: information display
When using the local checked out version of build-harness, display:
A notice that the local version is being used, including the exact directory where that version is located
A warning when that version is different than the current version of the default branch of the project, or a confirmation that hte latest version is being used
Feature Request: make this behavior a feature flag
More users are confused and "bitten" by this behavior than benefit from it. Therefore:
Make the default to be to use the auto-updated downloaded version when BUILD_HARNESS_AUTO_INIT is "true", with corresponding informational output
The text was updated successfully, but these errors were encountered:
Background
In order to ensure a known version of
build-harness
is run by various automation workflows, and to support development and testing ofbuild-harness
, if you have thebuild-harness
project checked out from GitHub and it is in the same directory tree at the same or higher level than your project, the checked out version will be used instead of the latest version.This leads to problems and confusion by end users when they have a checked out version and it is old.
Feature Request: information display
When using the local checked out version of
build-harness
, display:Feature Request: make this behavior a feature flag
More users are confused and "bitten" by this behavior than benefit from it. Therefore:
BUILD_HARNESS_AUTO_INIT
is "true", with corresponding informational outputThe text was updated successfully, but these errors were encountered: