f5f7e03d60
Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: Lauren Brose <labrose@github.com> Co-authored-by: Martin Lopes <martin389@github.com> Co-authored-by: Steve Guntrip <12534592+stevecat@users.noreply.github.com> Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Matt Butler <7584089+azenMatt@users.noreply.github.com>
1.3 KiB
1.3 KiB
title, intro, versions, topics
| title | intro | versions | topics | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Using keywords in issues and pull requests | Use keywords to link an issue and pull request or to mark an issue or pull request as a duplicate. |
|
|
Linking a pull request to an issue
To link a pull request to an issue to{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} show that a fix is in progress and to{% endif %} automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. For example, Closes #10 or Fixes octo-org/octo-repo#100.
- close
- closes
- closed
- fix
- fixes
- fixed
- resolve
- resolves
- resolved
For more information, see "Linking a pull request to an issue."
Marking an issue or pull request as a duplicate
To mark an issue or pull request as a duplicate, type "Duplicate of" followed by the issue or pull request number it duplicates in the body of a new comment. For more information, see "Marking issues or pull requests as a duplicate."