forked from TrueCloudLab/distribution
Forbid commenting on closed issues
Commenting on closed issues is rude and confusing. Most of the time, the issues aren't actually the same. It is much better to file a duplicate and merge them later when root cause has been identified than to have conflicting information throughout a ticket. Signed-off-by: Stephen J Day <stephen.day@docker.com>
This commit is contained in:
parent
7b0d831e6d
commit
e28be265d1
1 changed files with 1 additions and 0 deletions
|
@ -33,6 +33,7 @@ By following these simple rules you will get better and faster feedback on your
|
||||||
- please refrain from adding "same thing here" or "+1" comments
|
- please refrain from adding "same thing here" or "+1" comments
|
||||||
- you don't need to comment on an issue to get notified of updates: just hit the "subscribe" button
|
- you don't need to comment on an issue to get notified of updates: just hit the "subscribe" button
|
||||||
- comment if you have some new, technical and relevant information to add to the case
|
- comment if you have some new, technical and relevant information to add to the case
|
||||||
|
- __DO NOT__ comment on closed issues or merged PRs. If you think you have a related problem, open up a new issue and reference the PR or issue.
|
||||||
|
|
||||||
### If you have not found an existing issue that describes your problem:
|
### If you have not found an existing issue that describes your problem:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue