Misc docs cleanup and fixes (#155501)
This commit is contained in:
@@ -42,7 +42,7 @@ In the specific case of a bug with unclear steps to reproduce but very specific
|
||||
|
||||
If you recognize that this bug is a duplicate of an existing bug, add a reference to that bug in a comment, then close the bug. Skip the remaining steps. As you triage more and more bugs you will become more and more familiar with the existing bugs and so you will get better and better at marking duplicates in this way.
|
||||
|
||||
When closing the duplicate bug, the github issue tracker does not copy the list of people being notified on the closed bug into the original bug. This can matter, especially when asking on the original bug for things like reproduction steps. Consider cc'ing the author of the duplicate issue into the original issue, especially if we're still trying to determine reproduction steps for the issue.
|
||||
When closing the duplicate bug, the GitHub issue tracker does not copy the list of people being notified on the closed bug into the original bug. This can matter, especially when asking on the original bug for things like reproduction steps. Consider cc'ing the author of the duplicate issue into the original issue, especially if we're still trying to determine reproduction steps for the issue.
|
||||
|
||||
### Requests for help (documentation issues)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user