introduce the --tags-require-all flag #481
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
…on of the deploy scripts containing all the tags specified in --tags
|
Yes, make sense thanks for the PR! |
|
available in v0.11.37 |
Merged
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.
when using hardhat-deploy from command line I always lack the ability to execute the deployment scripts on the intersection of different tags, for exampleI would expect
npx hardhat deploy --tags v2_8,upgrade,l1
to only upgrade the v2.8 contracts on layer1
This PR introduces the --tags-require-all command line flag which changes the logic of how the --tags option is processed: comma is treated as logical AND instead of logical OR