itsscb/rust-analyzer
1
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer.git synced 2025-10-01 11:31:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #19035 from rust-lang/Veykril-patch-1

Browse Source 
Update outdated permissions section in the README.md
This commit is contained in:
Lukas Wirth 2025-01-26 07:12:02 +00:00 committed by GitHub
commit 2df4ecfc74
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/dev/README.md
View File

@ -269,19 +269,13 @@ Note: we tag releases by dates, releasing a patch release on the same day should
## Permissions ## Permissions
There are three sets of people with extra permissions: There are two sets of people with extra permissions:
* rust-analyzer GitHub organization [**admins**](https://github.com/orgs/rust-analyzer/people?query=role:owner) (which include current t-compiler leads). * The [rust-lang](https://github.com/rust-lang) team [t-rust-analyzer](https://github.com/rust-lang/team/blob/master/teams/rust-analyzer.toml).
Admins have full access to the org. This team has write access to the repository and merge queue permissions (note the repo itself is managed by infra admins).
* [**review**](https://github.com/orgs/rust-analyzer/teams/review) team in the organization.
Reviewers have `r+` access to all of organization's repositories and publish rights on crates.io.
They also have direct commit access, but all changes should via bors queue.
It's ok to self-approve if you think you know what you are doing! It's ok to self-approve if you think you know what you are doing!
bors should automatically sync the permissions.
Feel free to request a review or assign any PR to a reviewer with the relevant expertise to bring the work to their attention. Feel free to request a review or assign any PR to a reviewer with the relevant expertise to bring the work to their attention.
Don't feel pressured to review assigned PRs though. Don't feel pressured to review assigned PRs though.
If you don't feel like reviewing for whatever reason, someone else will pick the review up! If you don't feel like reviewing for whatever reason, someone else will pick the review up (but please speak up if you don't feel like it)!
* [**triage**](https://github.com/orgs/rust-analyzer/teams/triage) team in the organization. * The [rust-lang](https://github.com/rust-lang) team [t-rust-analyzer-contributors]([https://github.com/orgs/rust-analyzer/teams/triage](https://github.com/rust-lang/team/blob/master/teams/rust-analyzer-contributors.toml)).
This team can label and close issues. This team has general triaging permissions allowing to label, close and re-open issues.
Note that at the time being you need to be a member of the org yourself to view the links.