path/to/comm-central/.hg/hgrc
:live-cc
but you can use whatever you like. Using the standard label default-push
is 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 -a
to clean your local queue.hg in
to check if there are updates on the live server. (This isn't strictly necessary if you always do the next step.)hg pull -u
to download and apply the most recent changes.hg qpush
to apply only the patches you want to push to Live.hg qseries
to double check your have the right patches applied.hg qfinish --applied
to include all the currently applied patches in your local tree.hg out
to 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 hgrc
file) to push your applied patches to comm-central.hg pull
to download and apply the most recent changes.hg rebase -b my-bookmark-name -d XXX
to rebase your patches. Replace the XXX with the latest public revision.hg out -r my-bookmark-name
to 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-name
to push your applied patches to comm-central. Always specify a bookmark or revision to avoid sending more than one branch.DONTBUILD
tells 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 TREE
allows you to push to a closed tree. I hope you have permission!a=approver
You must specify who approved the changes on some trees (not comm-central).hg import -e https://bugzilla.mozilla.org/attachment.cgi?id=0000000
-e
flag as above, or hg commit --amend
to edit the commit message as necessary.moz-phab patch
: moz-phab patch --apply-to tip --no-bookmark --skip-dependencies D000000
--apply-to
argument adds the patch to a specific parent revision, in this case the tip revision.--no-bookmark
argument 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-dependencies
argument imports only the patch in question. Otherwise moz-phab
will 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 --amend
or hg histedit
to adjust commit messages as necessary.leave-open
keyword to the bug before landing. The bot will automatically remove the checkin-needed-tb
flag if it is set.approval-comm-beta
and approval-comm-esrXX
flags. 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.