Skip to content

Update link to "process outlined by Engineering Productivity"

Brett Walker requested to merge digitalmoksha-master-patch-f2b3 into master

Why is this change being made?

The link to process outlined by Engineering Productivity was incorrect. The correct link was provided in Slack, https://gitlab.slack.com/archives/C81PT2ALD/p1697520561314339?thread_ts=1697497598.601889&cid=C81PT2ALD

Q: are links with anchors checked for validity? For example in https://about.gitlab.com/handbook/engineering/gitlab-repositories/#creating-a-new-project, the process outlined by Engineering Productivity is referenced, which links to https://about.gitlab.com/handbook/engineering/quality/engineering-productivity/#requesting-new-projects-to-be-included, but there is not a valid section on that page.

I thought they would but it looks like they’re not. By the way I think the second link should go to https://about.gitlab.com/handbook/engineering/metrics/#updating-the-list-of-projects (good find!).

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

Merge request reports