Skip to content

Updated the automation request page for L&R

Tom Houston requested to merge tom-houston_LnR_automation_page_update into master

Why is this change being made?

The page as it stands now directs people to add features to Mechanizer, along with the steps on how to do that. Since there are efforts underway to get Mechanizer functionality integrated into the existing GitLab tools, I've updated the page to direct new functionality requests in the appropriate direction. As it stands now, Mechanizer is in a standby pattern, with only maintenance being done to it to ensure existing functionality continues to work with no additional features being incorporated.

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

Loading