id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36993	Clarify “N/A - typo” usage in PR field in contribution docs	JaeHyuckSa	JaeHyuckSa	"Hello!

Currently, Django requires most pull requests to reference a Trac ticket, and this is somewhat enforced through the contribution guidelines.

However, in practice, for low-risk PRs such as typo fixes, documentation updates, and small test additions, proceeding without a ticket under a “no ticket” approach is also encouraged in the guidelines.

Through a recent discussion on the [Django Forum](https://forum.djangoproject.com/t/introduce-a-minor-tag-for-low-risk-prs-that-dont-need-a-trac-ticket/44561/9), it seemed appropriate to make this intent more explicit by allowing contributors to write a reason in the ticket field when a PR is intentionally ticketless, such as:

- N/A - typo
- N/A - docs
- N/A - tests

With this in mind, I would like to suggest that we first explicitly document this pattern in the pull request template and related documentation.

(While it may be possible to validate guideline compliance later using GitHub Actions or similar approaches, I think it would be better to first establish a clear workflow standard through documentation and templates.)"	Cleanup/optimization	closed	Documentation	dev	Normal	fixed	pull_request		Ready for checkin	1	0	0	0	0	0