From b0490b0018e0748ccb14809043c1d1f9fe059210 Mon Sep 17 00:00:00 2001 From: Lin Jen-Shin Date: Tue, 7 Aug 2018 20:09:53 +0800 Subject: Update where to find the triaging bot --- CONTRIBUTING.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'CONTRIBUTING.md') diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ad8022e972f..0c483986270 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -377,13 +377,14 @@ on those issues. Please select someone with relevant experience from the the commit history for the affected files to find someone. We also use [GitLab Triage] to automate some triaging policies. This is -currently setup as a [scheduled pipeline] running on the [`gl-triage`] branch. +currently setup as a [scheduled pipeline] running on [quality/triage-ops] +project. [described in our handbook]: https://about.gitlab.com/handbook/engineering/issue-triage/ [issue bash events]: https://gitlab.com/gitlab-org/gitlab-ce/issues/17815 [GitLab Triage]: https://gitlab.com/gitlab-org/gitlab-triage -[scheduled pipeline]: https://gitlab.com/gitlab-org/gitlab-ce/pipeline_schedules/3732/edit -[`gl-triage`]: https://gitlab.com/gitlab-org/gitlab-ce/tree/gl-triage +[scheduled pipeline]: https://gitlab.com/gitlab-org/quality/triage-ops/pipeline_schedules/10512/edit +[quality/triage-ops]: https://gitlab.com/gitlab-org/quality/triage-ops ### Feature proposals -- cgit v1.2.1