Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Replace contributor-visible mentions of BPO in .github/* (GH-91426)

This commit is contained in:
Oleg Iarygin 2022-04-11 01:03:27 +03:00 committed by GitHub
parent 672e7de911
commit 98ff4a6877
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/CONTRIBUTING.rst vendored
View File

@ -44,7 +44,7 @@ comments they leave and their "Details" links, respectively. The key points of
our workflow that are not covered by a bot or status check are: our workflow that are not covered by a bot or status check are:
- All discussions that are not directly related to the code in the pull request - All discussions that are not directly related to the code in the pull request
should happen on bugs.python.org should happen on `GitHub Issues <https://github.com/python/cpython/issues>`_.
- Upon your first non-trivial pull request (which includes documentation changes), - Upon your first non-trivial pull request (which includes documentation changes),
feel free to add yourself to ``Misc/ACKS`` feel free to add yourself to ``Misc/ACKS``

4
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -7,10 +7,10 @@ Please read this comment in its entirety. It's quite important.
It should be in the following format: It should be in the following format:
``` ```
bpo-NNNN: Summary of the changes made gh-NNNNN: Summary of the changes made
``` ```
Where: bpo-NNNN refers to the issue number in the https://bugs.python.org. 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. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue.

2
.github/workflows/build.yml vendored
View File

@ -1,6 +1,6 @@
name: Tests name: Tests
# bpo-40548: "paths-ignore" is not used to skip documentation-only PRs, because # gh-84728: "paths-ignore" is not used to skip documentation-only PRs, because
# it prevents to mark a job as mandatory. A PR cannot be merged if a job is # it prevents to mark a job as mandatory. A PR cannot be merged if a job is
# mandatory but not scheduled because of "paths-ignore". # mandatory but not scheduled because of "paths-ignore".
on: on: