ReleaseEngineering/How To/Land Buildbot Master Changes: Difference between revisions

Jump to navigation Jump to search
Line 70: Line 70:
You will need to commit this merge. It's advisable to include a summary of what's been merged in the commit message. For example:
You will need to commit this merge. It's advisable to include a summary of what's been merged in the commit message. For example:
  hg commit -m "Merge bugs 616320, 616583, and 615097 from default branch"
  hg commit -m "Merge bugs 616320, 616583, and 615097 from default branch"
=== Pushing ===
When pushing, be sure that you're pushing the correct branches. When working with multiple branches it's good to check 'hg out' to ensure you're only pushing what you intend to. If you have changes on other branches you do not want to push you can use "-b" to restrict which branches are pushed. For example, to only push changes on the default branch of buildbotcustom, use the following:
hg push -b default ssh://hg.mozilla.org/build/buildbotcustom
You can also use "-b" as an argument to "hg out".
canmove, Confirmed users
6,441

edits

Navigation menu