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

docs: cleanup core merge info

Browse Source
This commit is contained in:
Rylan Polster 2021-05-19 12:50:34 -04:00
parent 817914fc04
commit 8edd4d3fac
No known key found for this signature in database
GPG Key ID: 46A744940CFF4D64
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/Homebrew-homebrew-core-Merge-Checklist.md
View File

@ -29,10 +29,14 @@ be in Homebrew Cask instead.
## Merging, rebasing, cherry-picking ## Merging, rebasing, cherry-picking
In most cases, you can simply approve a PR and an automatic merge (with bottles) For most PRs that make formula modifications, you can simply approve the PR and an automatic
will be performed by [@BrewTestBot](https://github.com/BrewTestBot). merge (with bottles) will be performed by [@BrewTestBot](https://github.com/BrewTestBot).
See [Brew Test Bot For Core Contributors](Brew-Test-Bot-For-Core-Contributors.md) for more information. See [Brew Test Bot For Core Contributors](Brew-Test-Bot-For-Core-Contributors.md) for more information.
Certain PRs may not be merged automatically by [@BrewTestBot](https://github.com/BrewTestBot),
even after they've been approved. This includes PRs with the `new formula`, `automerge-skip`,
and `linux-only` labels. To trigger a merge for these PRs, run `brew pr-publish`.
PRs modifying formulae that don't need bottles or making changes that don't PRs modifying formulae that don't need bottles or making changes that don't
require new bottles to be pulled should use GitHub's squash & merge or rebase & merge workflows. require new bottles to be pulled should use GitHub's squash & merge or rebase & merge workflows.
See the [table below](#how-to-merge-without-bottles) for more details. See the [table below](#how-to-merge-without-bottles) for more details.