aboutsummaryrefslogtreecommitdiffstats
path: root/docs/Migrating-A-Formula-To-A-Tap.md
diff options
context:
space:
mode:
authorEricFromCanada2017-03-25 22:53:33 -0400
committerEricFromCanada2017-03-25 22:53:33 -0400
commitdc7f74210a3d03d829cd459bf3171129f3e2f60d (patch)
tree97662357e8610c406314dfa770380d76b451dd04 /docs/Migrating-A-Formula-To-A-Tap.md
parent59fab56afdf6129c37ff30eb842bf7bff41348e0 (diff)
downloadbrew-dc7f74210a3d03d829cd459bf3171129f3e2f60d.tar.bz2
docs: code example reformatting
Add labeled fences to most code blocks, monospace terms where appropriate, omit "$" when referring to variables
Diffstat (limited to 'docs/Migrating-A-Formula-To-A-Tap.md')
-rw-r--r--docs/Migrating-A-Formula-To-A-Tap.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Migrating-A-Formula-To-A-Tap.md b/docs/Migrating-A-Formula-To-A-Tap.md
index ba5577056..08ba2df37 100644
--- a/docs/Migrating-A-Formula-To-A-Tap.md
+++ b/docs/Migrating-A-Formula-To-A-Tap.md
@@ -3,7 +3,7 @@
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 to 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 than existing formula (e.g. `brew audit --strict` must pass for that formula).
-2. Create a pull request to the original tap deleting the formula file and add it to `tap_migrations.json` with a commit message like `gv: migrating to homebrew/x11`.
+2. Create a pull request to the original tap deleting the formula file and add it to `tap_migrations.json` with a commit message like `gv: migrating to homebrew/science`.
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 a tap!