Files
awesome-python/.github/PULL_REQUEST_TEMPLATE.md
T
Vinta ChenandClaude 68b15a4644 docs: rephrase obvious-choice criterion in PR template
Reuses CONTRIBUTING.md's plainer 'would name when asked' phrasing instead of 'unprompted', per maintainer feedback that 'unprompted' didn't sound right.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-08-16 16:13:43 +08:00

27 lines
1.0 KiB
Markdown

## Project
[project-name](url)
## Checklist
- [ ] I read [CONTRIBUTING.md](https://github.com/vinta/awesome-python/blob/master/CONTRIBUTING.md) - awesome-python is a shortlist, not a catalog
- [ ] One project per PR
- [ ] PR title format: `Add project-name`
- [ ] Entry format: `- [pypi-name](https://github.com/owner/repo) - Description ending with period.`
- [ ] Display name is the PyPI package name
- [ ] Placed in an existing use case (new sections and subcategories are maintainer-only)
- [ ] Meets all Quality Requirements: active, stable, documented, at least 1 month old
## Which Tier
Pick one:
- [ ] **Obvious choice** - a tool an experienced Python developer would name when asked "what do I use for this?"
- [ ] **Challenger** - not yet the obvious choice, but a credible successor to one. Give adoption-trajectory evidence, not popularity alone.
Explain:
## Displacement
If the use case is at its cap, name the entry your project replaces and argue that yours does that entry's job better. One in, one out.