[GH-ISSUE #9] Pipelines for versioning correctly #3

New issue

Closed

opened 2026-03-03 00:06:02 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 00:06:02 +03:00

Owner

Originally created by @aurc on GitHub (Jun 25, 2022).
Original GitHub issue: https://github.com/aurc/loggo/issues/9

The exiting pipeline automatically increments the minor version of a tag upon merge from a feature to the the main branch.
This feature requires next level maturity for release planning, incorporating either a release or develop branch so that when
merged onto main it increments the major version number.

Additionally, add a version command to loggo that can display the current version. For that, a pipeline must
alter the source code to tag the newly generated tag version

Originally created by @aurc on GitHub (Jun 25, 2022). Original GitHub issue: https://github.com/aurc/loggo/issues/9 The exiting pipeline automatically increments the minor version of a tag upon merge from a `feature` to the the `main` branch. This feature requires next level maturity for release planning, incorporating either a `release` or `develop` branch so that when merged onto `main` it increments the major version number. Additionally, add a `version` command to `loggo` that can display the current version. For that, a pipeline must alter the source code to tag the newly generated tag version