InseeFr / InseeFr/DDI-Lifecycle-Java
Manage version from git tags
- Dominant language
- Java
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
- in the source code (model/build.gradle.kts), thes version should always be 0.0.1-SNAPSHOT for example
- at each pipeline which deploy, the version number is calculated as follows :
- take the version number of the last tag of the branch
- compute the next version number using commits messages (to be discuted)
- update the version number in the released files
- deploy
- tag the release with the calculated version
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with model/build.gradle.kts to understand the current fixed version, then inspect the pipeline configuration and existing release flow. The work is done when deployment derives the version from the latest branch tag and commit messages, updates released files, deploys, and creates the calculated release tag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100