From 18b835b2ac87c845c18dcaee0da1b6fdb20dacd9 Mon Sep 17 00:00:00 2001 From: Mike McQuaid Date: Fri, 23 Feb 2024 17:22:44 +0000 Subject: [PATCH] docs/New-Maintainer-Checklist: tell people to avoid forks. This was discussed at the AGM. It's no longer needed to avoid "cluttering up clones" because most users use the API for our main repositories now. It should also simplify security work in future because we can assume anyone who can create a branch on the main repository has write access rather than e.g. having a hardcoded list of maintainers we rely on. --- docs/New-Maintainer-Checklist.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/New-Maintainer-Checklist.md b/docs/New-Maintainer-Checklist.md index 4a7a5e4562..9f8ed646b1 100644 --- a/docs/New-Maintainer-Checklist.md +++ b/docs/New-Maintainer-Checklist.md @@ -44,10 +44,8 @@ A few requests: - Homebrew/brew: https://docs.brew.sh/Homebrew-brew-Maintainer-Guide - Homebrew/homebrew-core: https://docs.brew.sh/Homebrew-homebrew-core-Maintainer-Guide - Homebrew/homebrew-cask: https://docs.brew.sh/Homebrew-homebrew-cask-Maintainer-Guide -- Continue to create branches on your fork rather than in the main repository. - Note GitHub's UI will create edits and reverts on the main repository if you - make edits or click "Revert" on the Homebrew/brew repository rather than your - own fork. +- Create branches in the main repository rather than on your fork to ease collaboration + with other maintainers and allow security assumptions to be made based on GitHub access. - If still in doubt please ask for help and we'll help you out. - Please read: - https://docs.brew.sh/Maintainer-Guidelines