-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Correctly handle repo name when apply fine grained filtering #261
fix: Correctly handle repo name when apply fine grained filtering #261
Conversation
|
@tinder-maxwellelliott I'm thinking maybe it's better not to do this dance, but instead asking users to provide either apparent or canonical repo names with all the necessary |
@@ -1,9 +1,9 @@ | |||
package com.bazel_diff.bazel | |||
|
|||
import com.bazel_diff.log.Logger | |||
import java.util.Calendar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bazel run format
did this.
4a41de5
to
3979ee4
Compare
I think that sounds good to me, I am wary of any all-targets querying in bzlmod anyhow |
Cool. I will rework this PR a bit then. |
3979ee4
to
f8ddde0
Compare
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.