summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLin Jen-Shin <godfat@godfat.org>2018-07-23 22:41:31 +0800
committerLin Jen-Shin <godfat@godfat.org>2018-07-23 22:41:31 +0800
commitece48ec44e7d08bab08dc6ed1ba983630ebb4bfd (patch)
tree7d0daa767ef6e7fa65fb17e291cc6e1d6bea660b
parent1a959e1bf4269b3c74cb317d18bcc624436aabc5 (diff)
downloadgitlab-ce-docs-mention-how-it-is-used-in-gitlab-ce.tar.gz
Mention how we use gitlab-triagedocs-mention-how-it-is-used-in-gitlab-ce
-rw-r--r--CONTRIBUTING.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 631f80c6bd9..8793236ff83 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 in [`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