Fix flag tag_expr to follow same format as config and allow misc characters #117
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.
What's Changed
Tag expressions via
--tags-exprflag were too restrictive compared to config file tag definitions. Now allows special characters (hyphens, dots, etc.) matching config behavior.Technical Description
(,),!,&,|, and whitespacedocs/filtering-projects.mdExample: Tags like
v1.0,my-tag,@scope/packagenow work in expressions:mani run build --tags-expr 'frontend-v2 && !legacy.old'✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.