live-ccbut you can use whatever you like. Using the standard label
default-pushis not recommended – having to type the name of the repository helps prevent mistakes.
hg push, but let's not do that right now as a series of important checks need to happen before.
Bug 000000 - Description of the patch and fix. r=reviewer.
hg qpop -ato clean your local queue.
hg into check if there are updates on the live server. (This isn't strictly necessary if you always do the next step.)
hg pull -uto download and apply the most recent changes.
hg qpushto apply only the patches you want to push to Live.
hg qseriesto double check your have the right patches applied.
hg qfinish --appliedto include all the currently applied patches in your local tree.
hg outto see a list of patches that will be pushed to the Live server. Check your commit message(s) again.
hg push live-cc(or any shorthand you used in your
hgrcfile) to push your applied patches to comm-central.
hg pullto download and apply the most recent changes.
hg rebase -b my-bookmark-name -d XXXto rebase your patches. Replace the XXX with the latest public revision.
hg out -r my-bookmark-nameto see a list of patches that will be pushed to the Live server. Check only the patches you intend to send are listed. Check your commit message(s) again.
hg push live-cc -r my-bookmark-nameto push your applied patches to comm-central. Always specify a bookmark or revision to avoid sending more than one branch.
DONTBUILDtells the build system not to build on this push. Only the decision and linting tasks will happen, unless another process comes along and starts a build, such as the Daily automatic build.
CLOSED TREEallows you to push to a closed tree. I hope you have permission!
a=approverYou must specify who approved the changes on some trees (not comm-central).
hg import -e https://bugzilla.mozilla.org/attachment.cgi?id=0000000
-eflag as above, or
hg commit --amendto edit the commit message as necessary.
moz-phab patch --apply-to tip --no-bookmark --skip-dependencies D000000
--apply-toargument adds the patch to a specific parent revision, in this case the tip revision.
--no-bookmarkargument prevents a Mercurial bookmark from being created automatically. If you're just importing to land a patch, creating and then deleting a bookmark is just wasting your time.
--skip-dependenciesargument imports only the patch in question. Otherwise
moz-phabwill attempt to import all parent and child revisions in the Phabricator stack, including revisions that may already exist on your tree (and in this case fail miserably). You may want this to happen, in which case don't use this argument.
hg commit --amendor
hg histeditto adjust commit messages as necessary.
leave-openkeyword to the bug before landing. The bot will automatically remove the
checkin-needed-tbflag if it is set.
approval-comm-esrXXflags. Filling out the request form is not required. At an appropriate point approval will be granted (or denied!) and your patch will be landed for you.