Skip to content

Add clarification for contact requests

Armin Hergenhan requested to merge ahergenhan-main-patch-dd38 into main

Why is this change being made?

💡 I recently received a `Contact Request created by our security team during my CMOC shift. Although the documentation is clear how to contact the user(s) I was unsure if I should then close the issue or if there is a reason to keep it open. This update aims to calrify this situation.

  • Add clarification for contact requests and fix a broken link

Author and Reviewer Checklist

@kchappell would you please review this change?

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

Merge request reports