Skip to content

Clarify when merging might be blocked during a broken master incident

Luke Duncalfe requested to merge ld-mention-merges-can-be-blocked-during-broken-master into master

Why is this change being made?

This adds a clarification that sometimes a merge request can not be merged during a broken master incident because it is in a particular state, even if it meets the criteria outlined above that suggests it otherwise could be.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)

Merge request reports