Skip to content

DRAFT: Don't redact confidentials

What does this MR do and why?

This MR aims to fix #1160 (closed) by ensuring that when looking up the Milestone for the current Issue that we support confidential issues, which appears to be the root cause here.

I'm not an expert here, so this might be the incorrect fix. Am hoping for some advice from @rymai or @godfat-gitlab here, please 🙂🙏

cc @jennli

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

Closes #1160 (closed)

Edited by Ash McKenzie

Merge request reports