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

Add note about auditor to How-To-Open-a-Homebrew-Pull-Request.md

Browse Source
This commit is contained in:
Ryan Schumacher 2024-08-29 05:17:26 -05:00 committed by GitHub
parent 638a3dc3a3
commit 8c6aa176f6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/How-To-Open-a-Homebrew-Pull-Request.md
View File

@ -16,6 +16,15 @@ The type of change you want to make influences which of Homebrew's main reposito
### Core `brew` code pull request ### Core `brew` code pull request
Before getting started, please note that we cannot distribute every single piece of software and have to draw a line on “notability” somewhere. Of course, we would be happy to reconsider in the future. If you don't meet notability requirements you might consider [creating your own tap](https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap).
Notability [auditor](https://github.com/Homebrew/brew/blob/638a3dc3a33c4c2029db058cf3d399008621e973/Library/Homebrew/utils/shared_audits.rb) will fail on repositories that do not meet:
- **>29** days old
- **>29** forks
- **>29** watchers (Github only)
- **>74** stars
1. [Fork the Homebrew/brew repository on GitHub](https://github.com/Homebrew/brew/fork). 1. [Fork the Homebrew/brew repository on GitHub](https://github.com/Homebrew/brew/fork).
* This creates a personal remote repository that you can push to. This is needed because only Homebrew maintainers have push access to the main repositories. * This creates a personal remote repository that you can push to. This is needed because only Homebrew maintainers have push access to the main repositories.
2. Change to the directory containing your Homebrew installation: 2. Change to the directory containing your Homebrew installation: