Adopt towncrier to manage CHANGELOG updates
Open
Nobody has claimed this yet.
infrastructure
- Dominant language
- Python
- Stars
- 751
- Forks
- 324
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 3
Description
I've missed updating the changelog entries for a release twice now. It's probably a good idea to now update our processes to avoid that mode of failure.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's current changelog and release process, then compare them with towncrier's documented workflow. Define the required configuration, fragment convention, and release steps before making changes. Done means releases consistently generate the changelog without relying on a manual update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100