Skip to content

Clarify documentation component labels #1977

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tvmkamalesh3031-maker wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify documentation component labels #1977

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions triage/labels.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,11 @@ Component labels
These labels are mostly used to specify which :ref:`part of the codebase
<build_directory_structure>` is affected by the issue/PR:

For issues that only require documentation changes, use the
:gh-label:`docs` label. Code component labels such as
:gh-label:`stdlib` and :gh-label:`extension-modules` generally
do not apply unless the corresponding code is also affected.

* :gh-label:`stdlib`: for standard library modules in the :cpy-file:`Lib`
directory (written in Python).
* :gh-label:`extension-modules`: for standard library modules in the
Expand Down