From 9734d2aeae56bfe8e884f64d5200b2ebaafe17db Mon Sep 17 00:00:00 2001 From: Matt Sturgeon Date: Wed, 10 Sep 2025 22:08:10 +0100 Subject: [PATCH] Clarify what commit access is for in retirement PRs Many inactive committers seem confused by their retirement PRs, especially if they _have_ been active maintainers or have actively contributed in other ways. Hopefully, clearly stating which activities require commit access and which do not, will help avoid such confusion. --- scripts/retire.sh | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/scripts/retire.sh b/scripts/retire.sh index bffd73a..463f3bb 100755 --- a/scripts/retire.sh +++ b/scripts/retire.sh @@ -127,6 +127,10 @@ for login in *; do echo "This is an automated PR to retire @$login as a Nixpkgs committers due to not using their commit access for 1 year." echo "" echo "Make a comment with your motivation to keep commit access, otherwise this PR will be merged and implemented in 1 month." + echo "" + echo "> [!NOTE]" + echo -n "> Commit access is not required for most forms of contributing, including being a maintainer and reviewing PRs." + echo ' It is only needed for things that require `write` permissions to Nixpkgs, such as merging PRs.' } | effect gh api \ --method POST \ /repos/"$ORG"/"$MEMBER_REPO"/pulls \