nnnnnnnn

For pull requests, ensure that the corresponding issue is added before the title (gh-NNNNN: Title). Set all the relevant labels . Where appropriate, set the Assignees , Reviewers , Project fields, and possibly @mention relevant people.

You can link to issues and pull requests using gh-NNNNN (this form is preferred over #NNNNN). If the reference appears in a list, the link will be expanded to show the status and title of the issue/PR. When you create a PR that includes gh-NNNNN in the title, bedevere will automatically add a link to the issue in the first message.

2019年9月5日 · How do you think about stop using GH-NNNN in commit log and just use #NNNN instead? We need to be able to know which numbers reference github items after we move to the next version control system/service. CPython has already lasted longer than Mercurial, SVN, and at least two others older than I am.

2022年8月17日 · Currently, bedevere adds a convenient link to issue gh-NNNNN to the first message of a PR that includes gh-NNNNN in the title when the PR is created: However, if you look at the corresponding issue, the link to the PR is lost in the issue timeline among comments, metadata changes, and mentions from other issues and PRs:

2020年6月28日 · In addition, since we have switched to GitHub, and there may be overlapping issue numbers, bpo-NNNNN and gh-NNNNN are used to distinguish issues in the two namespaces. All bpo issues now also have a gh number, which is different.

2023年4月30日 · More semantically clear expression. 📚 Documentation preview 📚: https://cpython-previews--104021.org.readthedocs.build/

2024年3月11日 · # Pull Request title It should be in the following format: ``` gh-NNNNN: Summary of the changes made ``` Where: gh-NNNNN refers to the GitHub issue number. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

2024年9月10日 · # Pull Request title It should be in the following format: ``` gh-NNNNN: Summary of the changes made ``` Where: gh-NNNNN refers to the GitHub issue number. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

If this is a pull request in response to a pre-existing issue on the issue tracker, please make sure to reference the issue number using gh-NNNNN: prefix in the pull request title and #NNNNN in the description.