Sheriffing/How To/Merges: Difference between revisions

documented 'resume' parameter of bugherder
m (ChrisCooper moved page Sheriffing/How:To:Merges to Sheriffing/How To/Merges: More intuitive naming scheme)
(documented 'resume' parameter of bugherder)
Line 41: Line 41:
# Push your changes from Step 1.
# Push your changes from Step 1.
# Set the m-c tree back to "approval-required" in Treestatus. This is important because if we miss this, we risk unexpected pushes to mozilla-central since some people might think the open tree is intentional.
# Set the m-c tree back to "approval-required" in Treestatus. This is important because if we miss this, we risk unexpected pushes to mozilla-central since some people might think the open tree is intentional.
# Use Bugherder to mark and failures as usual for your push.
# Use Bugherder to mark and failures as usual for your push. If all bugs failed to get marked, entered Bugzilla API might be wrong. Close the tab and try with a new one. If only some failed, open Bugherder for that push again and append <code>&resume=1</code> to the url.
# Now when you merge from mozilla-inbound you get the note that you need to merge.
# Now when you merge from mozilla-inbound you get the note that you need to merge.
Confirmed users
571

edits