versionize / versionize/versionize
Date Versioning with versionize?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 380
- Forks
- 51
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
Hi,
I love versionize, it makes it easy to standardize our commits, bump versions and create changelogs based on the commits.
For some solutions we use Date Versioning like 2025.01.09-1.
Is it possible maybe by parameter --dateversioning to bump Date versioning.
versionize could just check the parameters that have the intended commit messages, and just bump the version to the latest date from the latest commit. It would still output a changelog with the date version and would list all fixes/features in it.
Or are there other things that I need to consider?
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 reviewing versionize’s existing CLI versioning parameters and its semver and changelog flow. Define the expected --dateversioning behavior around commit dates, date-based version output, and changelog entries, then validate the design against the repository’s current versioning behavior; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100