open-horizon / open-horizon/devops
Automation: Create GHA to generate CHANGELOG entries aligned with a release
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Shell
- Stars
- 12
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
TBD
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
The issue body is only “TBD” and names no files, tests, or workflow entry points. First clarify how releases are represented, which CHANGELOG format is required, and what GitHub Actions trigger should generate entries. Done should be defined by an agreed workflow and verification method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100