Skip to content

Create a new page for "Guidelines for automation and access tokens"

Rémy Coutable requested to merge new-page-guidelines-for-automation-and-access-tokens into master

Why is this change being made?

Introduce a new page for "Guidelines for automation and access tokens" where we describe:

  • best practices for access tokens
  • automations we have in place
  • when and how to request a new service account
  • current initiatives to improve the status quo

Solves https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/904, part of https://gitlab.com/groups/gitlab-org/quality/-/epics/17.

Review app:

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct 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 in 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.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)
Edited by Rémy Coutable

Merge request reports