Skip to content

Update Verification guidelines for Compliance

Phil Calder requested to merge compliance-verification-by-author into master

Why is this change being made?

There may be cases where it makes sense for the MR author / issue assignee to verify their own change. This MR starts the discussion around this.

WDYT @gitlab-org/govern/compliance - is there a need in some cases to bypass the triage-ops verification process? (Please feel free to dis/agree)

Note: There would also need to be a change to the triage-ops policy if this is merged.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (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 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
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Phil Calder

Merge request reports