diff options
| author | Sahdev Zala <spzala@us.ibm.com> | 2021-02-22 10:52:39 -0500 |
|---|---|---|
| committer | Sahdev Zala <spzala@us.ibm.com> | 2021-02-22 10:52:39 -0500 |
| commit | b9c18d3a6c4553d471670cf5b59de3bd9b06f849 (patch) | |
| tree | 3871997fc51bc948bf4e9c826180f0c7bf62c7ba | |
| parent | 665f4ea969377c460551995582251f28c3589867 (diff) | |
New PR for an already assigned issues
Clarify when to create a PR to address an issue by a new contributor when
the issue is already assigned to someone else.
| -rw-r--r-- | contributors/guide/issue-triage.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/contributors/guide/issue-triage.md b/contributors/guide/issue-triage.md index 29c2d9ec..7cf6894e 100644 --- a/contributors/guide/issue-triage.md +++ b/contributors/guide/issue-triage.md @@ -218,6 +218,8 @@ Components are divided among [Special Interest Groups (SIGs)](/sig-list.md). [Th ### Self-Assigning If you think you can fix the issue, assign it to yourself with *just* the `/assign` label. If you cannot self-assign for permissions-related reasons, leave a comment that you'd like to claim it and work on creating a PR. +When an issue already has an assignee, **Do Not** assign it to yourself or create a PR without talking to the existing assignee or going through the [Follow Up](#Step-Five:-Follow-Up) steps as described in this document. Creating a PR, when someone else is working on it, is not a good practice and should be discouraged. + ## Step Five: Follow Up ### If no PR is created for an Issue Within the Current Release Cycle If you see any issue which is owned by a developer but a PR is not created in 30 days, a Triage engineer should contact the issue owner and ask them to either create a PR or release ownership. |