Repository navigation
Feature: Clarify that docs issues typically don't get version labels #1674
Description
Describe the enhancement or feature you would like
In learning how to label / triage came across a docs issue where I got the labels fairly off and I would like to add more details to the devguide to help future triagers get it right the first time. In particular:
docsissues don't typically get version labels (Those tend to only go with code changes)- If there's no code change needed then
stdlib,extension-modules, etc. tend not to apply.
Describe alternatives you have considered
No response
Additional context
No response
Activity
StanFromIreland commentedon Oct 28, 2025
See also PR #1613 which adds a section on them.
pavithraramesh5500-ship-cse commentedon Oct 19, 2026
sarthakkondawar2007 commentedon Oct 23, 2026
Hi! I'd like to contribute to this issue.
I noticed that the current label documentation explains version and component labels but doesn't explicitly clarify how they apply to documentation-only issues.
I also noticed the related PR #1613. Would it be appropriate to work on the remaining clarification in this issue, particularly when version labels and component labels such as
stdlibandextension-modulesshould be applied?I'd be happy to prepare a focused documentation change based on your guidance.