Skip to content

Update community contribution link

Why is this change being made?

Please see the 15.8 retrospective note here: #14374 (comment 1276894793)

This MR updates the link for checking the number of merged community contributor MRs per release cycle. The old link used a search within GitLab that only counted MRs tagged with the milestone label but the majority of MRs do not have this label. The new link uses a Sisense chart that gives the full number of merged community contributor MRs during the release cycle.

If there are any other places this instruction needs to be updated please make note, thank you! :-)

Author Checklist

  • 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
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports