From 0646d4acf3111b984767125f0fde36292290e883 Mon Sep 17 00:00:00 2001 From: Jieyou Xu Date: Thu, 30 Oct 2025 23:20:29 +0800 Subject: [PATCH] Clarify `team` repo approval requirements --- src/infra/team-maintenance.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/infra/team-maintenance.md b/src/infra/team-maintenance.md index a34f6392..4eff3f57 100644 --- a/src/infra/team-maintenance.md +++ b/src/infra/team-maintenance.md @@ -43,6 +43,9 @@ The following changes must be approved and merged by a `team-repo-admin`: added, the team-repo-admins are expected to exercise their understanding of which team owns the repository, when in doubt asking for clarification and codifying in a comment in the relevant repository. +* Changing `bors.rust.review` permissions +* Changing `perf` permissions +* Changing `crater` permissions On the other hand, changes to the configuration or automation of repositories may be approved and merged by `infra-admins`: @@ -51,6 +54,10 @@ may be approved and merged by `infra-admins`: * This includes granting bots access to the repository. * Changing the [repository branch protections](https://github.com/rust-lang/team/blob/master/docs/toml-schema.md#repository-branch-protections) +Granting a team write access to `rust-lang/rust` requires approval from both an +`infra-admin` and a `team-repo-admin` as that repository is particularly +sensitive. + ### Source code changes The team repository additionally contains code to transform and validate the