From 1b0eaa093af319439f611d49f328030be07c6136 Mon Sep 17 00:00:00 2001 From: Jakob Borg Date: Sat, 13 Sep 2025 15:42:54 +0200 Subject: [PATCH] chore(policy): increase power & responsibility for maintainers This adds a rule where a maintainer can merge a PR on their own even in non-trivial cases, which we (I) already do as-is today, but by breaking the rules instead of following them. This just codifies that behavior. If we get to a point where it's no longer necessary, that'd be cool. Signed-off-by: Jakob Borg --- .policy.yml | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/.policy.yml b/.policy.yml index 7f32da007..00de07419 100644 --- a/.policy.yml +++ b/.policy.yml @@ -8,17 +8,20 @@ policy: approval: - subject is conventional commit - - project metadata requires maintainer approval + - or: + - project metadata requires maintainer approval + - a maintainer claims responsibility - or: - is approved by a syncthing contributor - is a translation or dependency update by a contributor - is a trivial change by a contributor + - a maintainer claims responsibility - # Additionally, contributors can disapprove of a PR + # Additionally, maintainers can disapprove of a PR disapproval: requires: teams: - - syncthing/contributors + - syncthing/maintainers # The rules for the policy are described below. @@ -96,3 +99,13 @@ approval_rules: has_author_in: teams: - syncthing/contributors + + # A member of the maintainers group can take responsibility by adding the + # appropriate label. + - name: a maintainer claims responsibility + if: + has_labels: + - maintainer-responsibility + has_author_in: + teams: + - syncthing/maintainers