admin/brew
1
0
Fork 0
Code Issues Packages Projects Releases 6 Wiki Activity

docs/New-Maintainer-Checklist: tell people to avoid forks.

Browse Source 
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.
This commit is contained in:
Mike McQuaid 2024-02-23 17:22:44 +00:00
parent d3ef383753
commit 18b835b2ac
No known key found for this signature in database
GPG Key ID: 3338A31AFDB1D829
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/New-Maintainer-Checklist.md
View File

@ -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