Confirmed users
571
edits
Sheriffing/How To/Merges: Difference between revisions
added configuration to disable WebIDL / DOM peer review requirement
(documented 'resume' parameter of bugherder) |
(added configuration to disable WebIDL / DOM peer review requirement) |
||
| Line 43: | Line 43: | ||
# 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. | # 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. | ||
= Issues = | |||
== Push rejected: DOM peer review needed == | |||
(fix still needs to be verified in production) | |||
If the server rejects the push with the merge and complains that a changeset needs review by a DOM peer, you can disable this check. The issue should only affect merges with changesets which initially landed on autoland. Temporarily add this to the <code>hgrc</code> file in the <code>.hg</code> folder of the repository: | |||
<code>mozilla.check.webidl_check = false</code> | |||