Materials-Consortia / Materials-Consortia/optimade-python-tools
Changelog generator cannot handle backported releases
Open
Nobody has claimed this yet.
bug
deployment
- Dominant language
- Python
- Stars
- 91
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Not sure its worth putting any effort into this, beyond manually updating at least the release changelogs on GitHub.
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 locating the changelog generator and reviewing how it handles backported releases. Compare its output with the manually updated release changelogs on GitHub; done would mean the generator can produce correct changelogs for backported releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100