docs/New-Maintainer-Checklist: tell people to avoid forks. #16734
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
issyl0
approved these changes
Feb 23, 2024
ZhongRuoyu
approved these changes
Feb 23, 2024
p-linnane
approved these changes
Feb 23, 2024
Still relevant for Homebrew/brew but we should probably not be pulling every branch anyway. |
The forking UI now includes a "Copy the master branch only" checkbox that's enabled by default. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.