-
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
Do not watch .netrc
in read_netrc
#22125
Closed
Closed
Conversation
This file contains 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
Modifying auth information should not result in a repo rule being reevaluated after a successful evaluation. This regressed in a5376aa.
@bazel-io fork 7.2.0 |
github-actions
bot
added
the
awaiting-review
PR is awaiting review from an assigned reviewer
label
Apr 25, 2024
sgowroji
added
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
awaiting-user-response
Awaiting a response from the author
and removed
awaiting-review
PR is awaiting review from an assigned reviewer
labels
Apr 25, 2024
@fmeum looks like tests are failing due to a lockfile being out of date.
|
Thanks @mortenmj, I updated the lockfiles. |
fmeum
added
awaiting-review
PR is awaiting review from an assigned reviewer
and removed
awaiting-user-response
Awaiting a response from the author
labels
Apr 25, 2024
I would appreciate it if this could be considered for inclusion in 7.1.2 |
meteorcloudy
approved these changes
Apr 26, 2024
meteorcloudy
added
awaiting-PR-merge
PR has been approved by a reviewer and is ready to be merge internally
and removed
awaiting-review
PR is awaiting review from an assigned reviewer
labels
Apr 26, 2024
@bazel-io fork 7.1.2 |
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this pull request
Apr 29, 2024
Modifying auth information should not result in a repo rule being reevaluated after a successful evaluation. This regressed in a5376aa. Fixes bazelbuild#22118 Closes bazelbuild#22125. PiperOrigin-RevId: 629182408 Change-Id: I0c553e9ded72230b647a37203d51ba779976d7fc
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this pull request
Apr 29, 2024
Modifying auth information should not result in a repo rule being reevaluated after a successful evaluation. This regressed in a5376aa. Fixes bazelbuild#22118 Closes bazelbuild#22125. PiperOrigin-RevId: 629182408 Change-Id: I0c553e9ded72230b647a37203d51ba779976d7fc
sgowroji
removed
the
awaiting-PR-merge
PR has been approved by a reviewer and is ready to be merge internally
label
Apr 30, 2024
github-merge-queue bot
pushed a commit
that referenced
this pull request
Apr 30, 2024
Modifying auth information should not result in a repo rule being reevaluated after a successful evaluation. This regressed in a5376aa. Fixes #22118 Closes #22125. PiperOrigin-RevId: 629182408 Change-Id: I0c553e9ded72230b647a37203d51ba779976d7fc Commit 3fc76be Co-authored-by: Fabian Meumertzheim <[email protected]>
@mortenmj Looks like we are not planning for 7.1.2 anymore. But, this will be included in 7.2.0. |
Wyverald
pushed a commit
that referenced
this pull request
May 6, 2024
Modifying auth information should not result in a repo rule being reevaluated after a successful evaluation. This regressed in a5376aa. Fixes #22118 Closes #22125. PiperOrigin-RevId: 629182408 Change-Id: I0c553e9ded72230b647a37203d51ba779976d7fc Commit 3fc76be Co-authored-by: Fabian Meumertzheim <[email protected]>
Kila2
pushed a commit
to Kila2/bazel
that referenced
this pull request
May 13, 2024
Modifying auth information should not result in a repo rule being reevaluated after a successful evaluation. This regressed in a5376aa. Fixes bazelbuild#22118 Closes bazelbuild#22125. PiperOrigin-RevId: 629182408 Change-Id: I0c553e9ded72230b647a37203d51ba779976d7fc
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.
Modifying auth information should not result in a repo rule being reevaluated after a successful evaluation. This regressed in a5376aa.
Fixes #22118