glacier-modding / glacier-modding/NavKit
Update release workflow to allow updating the version number using conventional commits
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The release workflow should automatically handle commit messages in the conventional commits format and update the root CMakeLists.txt and NavKitConfig.h with the new version number, as well as make a new tag and release automatically with the commit messages as part of the release description.
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 locating and reading the existing release workflow, then inspect the root CMakeLists.txt and NavKitConfig.h version definitions alongside the Conventional Commits summary. Done means qualifying commit messages update both version locations, create a tag and release automatically, and include the commit messages in the release description.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, git, github-actions
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100