-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[7.0.1] Avoid emitting canonical labels into generated repos #20825
Milestone
Comments
Cherry-pick was attempted, but there may be merge conflict(s). Please resolve manually. |
/cc @fmeum |
fmeum
added a commit
to fmeum/bazel
that referenced
this issue
Jan 10, 2024
As long as bazelbuild#20722 isn't resolved, the canonical name for the given apparent name can change without the repo rule being refetched. Closes bazelbuild#20810. PiperOrigin-RevId: 597048244 Change-Id: I225424cc32e572b26c6d6e76e2c09c4d2e6a4ba6 Closes bazelbuild#20825
@meteorcloudy I submitted #20840. |
fmeum
added a commit
to fmeum/bazel
that referenced
this issue
Jan 10, 2024
As long as bazelbuild#20722 isn't resolved, the canonical name for the given apparent name can change without the repo rule being refetched. Closes bazelbuild#20810. PiperOrigin-RevId: 597048244 Change-Id: I225424cc32e572b26c6d6e76e2c09c4d2e6a4ba6 Closes bazelbuild#20825
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Forked from #20810
The text was updated successfully, but these errors were encountered: