Typical issue workflow is the person working on the bug resolves it, and the person who opened the bug is the one who decides if the resolution is acceptable. If it is, they close it. If not, they re-open the bug for further discussion/work/wrangling. The exception to this is when a bug is a duplicate, … Read more
Closes #1, closes #2, closes #3; rest of commit message. The closes clauses can be anywhere in the message and fixes is a valid synonym: This fixes a memory leak in foo() that closes #4, also fixes #5 which is a duplicate. The following used to work, but nowadays only references issues #2 and #3. … Read more
Adding a pull request to an existing upstream issue is easy assuming you forked using the normal github means. Simply reference the issue in your commit message using any of the supported keywords: close closes closed fix fixes fixed resolve resolves resolved For example: “this commit fixes #116” The text referencing the issue does not … Read more
No, the github API only allows you to open/close/reopen issues. Here’s the Issues API docs.
To reference a commit, simply write its SHA-hash, and it’ll automatically get turned into a link. See also: The Autolinked references and URLs / Commit SHAs section of Writing on GitHub.