kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5540 from spzala/issueprtime 

New PR for an already assigned issues
This commit is contained in:
Kubernetes Prow Robot 2021-03-01 16:09:25 -08:00 committed by GitHub
parent 94a88b1e8d b9c18d3a6c
commit 4c9ef2d135
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/guide/issue-triage.md
View File

@ -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.