Set `GITLAB_API_TOKEN` from `GITLAB_BOT_AUTOMATED_TRIAGE_TOKEN`
What does this MR do and why?
Triage.api_client
is using GITLAB_API_TOKEN
, so we set it from
GITLAB_BOT_AUTOMATED_TRIAGE_TOKEN
as we don't want to un-protect
the actual GITLAB_API_TOKEN
CI/CD variable set in the project.
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-with-a-dry-run on how to perform dry-runs.
Action items
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-
Edited by Rémy Coutable