diff options
-rw-r--r-- | docs/dev/README.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md index 2795f6b5c..4a2f9feb3 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md | |||
@@ -292,3 +292,17 @@ Release steps: | |||
292 | 4. Tweet | 292 | 4. Tweet |
293 | 5. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule. | 293 | 5. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule. |
294 | Self-approve the PR. | 294 | Self-approve the PR. |
295 | |||
296 | # Permissions | ||
297 | |||
298 | There are three sets of people with extra permissions: | ||
299 | |||
300 | * rust-analyzer GitHub organization **admins** (which include current t-compiler leads). | ||
301 | Admins have full access to the org. | ||
302 | * **review** team in the organization. | ||
303 | Reviewers have `r+` access to all of organization's repositories and publish rights on crates.io. | ||
304 | They also have direct commit access, but all changes should via bors queue. | ||
305 | It's ok to self-approve if you think you know what you are doing! | ||
306 | bors should automatically sync the permissions. | ||
307 | * **triage** team in the organization. | ||
308 | This team can label and close issues. | ||