semantic-release / semantic-release/release-notes-generator
Question - How do you generate multiple changelogs in different formats?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 368
- Forks
- 55
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
I use conventional commits in my project for the change-log and play store "what's new" section https://github.com/sschueller/peertube-android/blob/develop/.releaserc.yml
Right now I copy the same data that is in appended to the changelog.md to the play store listing. However that doesn't support the markdown format and Google will most likely reject my future app updates if I have version number and commit hashes in there.
How can I produce a second change-log in a simple list format for the play store? I'd rather not make some complex bash thing to remove what I don't want if it can be done directly.
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 with the linked .releaserc.yml and the release-notes-generator configuration it uses. Check the plugin's documented output and formatting options first; done would mean a supported way to produce a simple Play Store list separately from changelog.md.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100