Skip to content

Document new permissions #6906

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Dec 16, 2020
Merged

Document new permissions #6906

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6e9023c
Document new permissions
matklad Dec 16, 2020
675390e
Update docs/dev/README.md
matklad Dec 16, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/dev/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -292,3 +292,17 @@ Release steps:
4. Tweet
5. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule.
Self-approve the PR.

# Permissions

There are three sets of people with extra permissions:

* rust-analyzer GitHub organization **admins** (which include current t-compiler leads).
Admins have full access to the org.
* **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.
Copy link
Member

@bjorn3 bjorn3 Dec 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should go via the bors

It's ok to self-approve if you think you know what you are doing!
bors should automatically sync the permissions.
* **triage** team in the organization.
This team can label and close issues.