[TODO] Find an easier way to maintain or automate the changelog
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
At one point, I had a changelog generator going, which wasn't perfect but gave summaries for each version. However, to use that, there should be instructions written up to make it clear of when to run that script. It's possible we could use something like this.
Even MORE ideal would be to auto-generate / update this as part of a publishing action automated by Github Actions.
Contributor guide
No contributing guide indexed for this repository
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 previously used changelog generator and the publishing process described in the issue. Compare documenting when to run it, using conventional-changelog-cli, and automating changelog updates with GitHub Actions; done means an agreed approach is documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100