-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Don't show fixup warnings during bazel mod tidy
#24729
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
Closed
Closed
Conversation
This file contains hidden or 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
The warnings tell the user to run `bazel mod tidy`, which is very confusing.
meteorcloudy
approved these changes
Dec 18, 2024
Collaborator
Author
|
@bazel-io fork 8.0.1 |
Collaborator
Author
|
@bazel-io fork 7.5.0 |
This was referenced Dec 18, 2024
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this pull request
Dec 19, 2024
The warnings tell the user to run `bazel mod tidy`, which is very confusing. Fixes bazelbuild#24495 Closes bazelbuild#24729. PiperOrigin-RevId: 708007222 Change-Id: I60dc889281a776bbf08a7f9537272d7692cce1d8
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 20, 2024
The warnings tell the user to run `bazel mod tidy`, which is very confusing. Fixes #24495 Closes #24729. PiperOrigin-RevId: 708007222 Change-Id: I60dc889281a776bbf08a7f9537272d7692cce1d8 Commit 455ddb7 Co-authored-by: Fabian Meumertzheim <[email protected]>
fmeum
added a commit
to fmeum/bazel
that referenced
this pull request
Jan 7, 2025
The warnings tell the user to run `bazel mod tidy`, which is very confusing. Fixes bazelbuild#24495 Closes bazelbuild#24729. PiperOrigin-RevId: 708007222 Change-Id: I60dc889281a776bbf08a7f9537272d7692cce1d8 (cherry picked from commit 455ddb7)
fmeum
added a commit
to fmeum/bazel
that referenced
this pull request
Jan 7, 2025
The warnings tell the user to run `bazel mod tidy`, which is very confusing. Fixes bazelbuild#24495 Closes bazelbuild#24729. PiperOrigin-RevId: 708007222 Change-Id: I60dc889281a776bbf08a7f9537272d7692cce1d8 (cherry picked from commit 455ddb7)
fmeum
added a commit
to fmeum/bazel
that referenced
this pull request
Jan 29, 2025
The warnings tell the user to run `bazel mod tidy`, which is very confusing. Fixes bazelbuild#24495 Closes bazelbuild#24729. PiperOrigin-RevId: 708007222 Change-Id: I60dc889281a776bbf08a7f9537272d7692cce1d8
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.
The warnings tell the user to run
bazel mod tidy, which is very confusing.Fixes #24495