diff options
| author | Sahdev P. Zala <spzala@us.ibm.com> | 2018-07-21 15:18:33 -0400 |
|---|---|---|
| committer | Sahdev P. Zala <spzala@us.ibm.com> | 2018-07-23 16:09:16 -0400 |
| commit | 198442b3152994eaace96e7d8576ca3ee9f4f1c1 (patch) | |
| tree | 04a92be6d1c75defcf15834b60c6b8312210dcfb | |
| parent | e09c6f49bb0186860d31c292cf9752ffeb80c028 (diff) | |
Mention fejta bot in the triage guidelines
Since the fejta bot now actively triaging and closing issues, we should
mention it in the triage guidelines and if it has any impact on the usage of
the guidelines for closing issues. It should be helpful to anyone referencing
the guidelines specially to the new triagers.
| -rw-r--r-- | contributors/guide/issue-triage.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/contributors/guide/issue-triage.md b/contributors/guide/issue-triage.md index 7534498b..6eacc9f1 100644 --- a/contributors/guide/issue-triage.md +++ b/contributors/guide/issue-triage.md @@ -226,3 +226,11 @@ order to work on it. A triage engineer should add these labels appropriately. Kubernetees GitHub Org members can search [open issues per these labels](https://github.com/kubernetes/kubernetes/labels?utf8=%E2%9C%93&q=triage%2F+kind%2Fsupport+is%3Aopen) to find ones that can be quickly closed. + +Also note that, `fejta-bot` will add `lifecycle/stale` label to issues with no +activity for 90 days. Such issues will be eventually auto closed if the label is +not removed with the `/remove-lifecycle stale` label or prevented with the +`/lifecycle frozen` label. Refer to the `fejta-bot` added comments in the issue +for more details. It is fine to add any of the `triage/*` labels described in +this issue triage guidelines to issues triaged by the `fejta-bot` for a better +understanding of the issue and closing of it. |