diff options
| author | Rémy Coutable <remy@rymai.me> | 2018-07-23 16:33:09 +0000 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2018-07-23 16:33:09 +0000 |
| commit | 4636bebb6823d0bf69230edc4c20300d1978948f (patch) | |
| tree | 0bf48d88fcdc06be40d8d017a4953f1f44ccda16 | |
| parent | 92802e51075f485ce2aa80d19f40688f1dd95fb7 (diff) | |
| parent | efb86c66d4da03ed6e928fe2f7e876e590c43d3f (diff) | |
| download | gitlab-ce-4636bebb6823d0bf69230edc4c20300d1978948f.tar.gz | |
Merge branch 'docs-mention-how-it-is-used-in-gitlab-ce' into 'master'
Mention how we use gitlab-triage
See merge request gitlab-org/gitlab-ce!20787
| -rw-r--r-- | CONTRIBUTING.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 631f80c6bd9..ad8022e972f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -376,8 +376,14 @@ on those issues. Please select someone with relevant experience from the [GitLab team][team]. If there is nobody mentioned with that expertise look in 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. + [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 ### Feature proposals |