unify ci/ and hack/ as bass/ #149
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
previously, ci/ was for things "run by ci" and hack/ was for things "run by devs". ci/ would typically prefer to start with a SHA and fetch a reproducible input, while hack/ would always run with host paths. with the last slew of changes it's pretty easy to unify them so they take a `src` value on stdin, which can be easily passed with -i src=./ during dev.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
previously, ci/ was for things "run by ci" and hack/ was for things "run by devs". ci/ would typically prefer to start with a SHA and fetch a reproducible input, while hack/ would always run with host paths.
with the last slew of changes it's pretty easy to unify them so they take a
srcvalue on stdin, which can be easily passed with-i src=./during dev.