brew/docs/Migrating-A-Formula-To-A-Tap.md
EricFromCanada d615899ca9
Contributors docs: content & formatting updates
Update How-To-Open-a-Homebrew-Pull-Request.md

Update Acceptable-Formulae.md

Update Acceptable-Casks.md

Update License-Guidelines.md

Update Versions.md

Update Versions.md

Update Deprecating-Disabling-and-Removing-Formulae.md

Update Node-for-Formula-Authors.md

Update Python-for-Formula-Authors.md

Update Brew-Livecheck.md

Update Migrating-A-Formula-To-A-Tap.md

Update Rename-A-Formula.md

Update How-to-Create-and-Maintain-a-Tap.md

Update Brew-Test-Bot.md

Update Typechecking.md
2022-11-16 09:03:12 -05:00

955 B

Migrating a Formula to a Tap

There are times when we may wish to migrate a formula from one tap into another tap. To do this:

  1. Create a pull request on the new tap adding the formula file as-is from the original tap. Fix any test failures that may occur due to the stricter requirements for new formulae compared to existing formulae (e.g. brew audit --strict must pass for that formula).
  2. Create a pull request on the original tap deleting the formula file and adding it to tap_migrations.json with a commit message like gv: migrate to homebrew/core.
  3. Put a link for each pull request in the other pull request so the maintainers can merge them both at once.

Congratulations, you've moved a formula to another tap!

For Homebrew maintainers, formulae should only ever be migrated into and within the Homebrew organisation (e.g. from homebrew/core to homebrew/cask, or from a third-party tap to homebrew/core), and never out of it.