Grant rust-analyzer team write access to rust-lang/rust - #1841
Merged
Conversation
jieyouxu
requested review from
Mark-Simulacrum,
emilyalbini,
jdno and
marcoieni
as code owners
May 24, 2025 10:51
Dry-run check results |
emilyalbini
approved these changes
May 24, 2025
Member
|
infra-admins approval given, let's wait for a team repo admin. |
Mark-Simulacrum
approved these changes
May 24, 2025
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
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.
rust-analyzeralready has bors r+ permissions onrust-lang/rustteam/teams/rust-analyzer.toml
Lines 27 to 28 in c7359de
rust-lang/rust, which seems very weird.We should give
rust-analyzerteam members write access since they already haver+. Noticed while trying to figure out why rust-lang/triagebot#2010 is a problem.cc @Veykril