fix: Correctly handle repo name when apply fine grained filtering #261
+28
−31
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
--useCquery
or setting--bazelCommandOptions=--consistent_labels
(while not using--useCquery
), canonical repo name must be used for--fineGrainedHashExternalRepos
, but with a leading@
. In that case, we cannot remove all@
from source target name, otherwise nothing will never match--fineGrainedHashExternalRepos
.This PR fixes that by asking users to always provide apparent or canonical repo name (with
@
or@@
).After this fix, it is not strictly necessary to use canonical name when
--useCquery
because we compare repo name without any@
, but to keep it easier for users to follow, the readme says otherwise.Note that this is a breaking change.