Use bumpversion to manage versions across build systems
Open
Nobody has claimed this yet.
enhancement
good first issue
help wanted
- Dominant language
- C++
- Stars
- 21
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Using a tool like bumpversion can keep this kind of special wiring logic to a minimum, but no need to hold up this PR on that. Someone can circle back to that in the future if it's interesting.
Originally posted by @bretbrownjr in https://github.com/cps-org/cps-config/pull/82#discussion_r1653003079
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
Review PR #82 and its discussion to understand the existing version wiring across build systems; no source files or tests are identified in this issue. Done means using bumpversion to manage versions consistently without the special wiring logic.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100