search

K-Phoen / semver-release-action

GitHub Action to automatically create SemVer compliant releases based on PR labels.
MIT License
85 stars 38 forks source link

Allow multiple semver incremental systems based on branch/tag format #43

Open amirs-kov opened 3 years ago

amirs-kov commented 3 years ago

In our repository we currently want to have to semver releases for two different products the advance in different timelines. To do so, we want our semver incrementing separately based on the branch or on the tag_format as both of them are different in our case. For example, say you have two products and a version to each of them: v0.0.1-a and v0.0.1-b and each of them is released when merging to different branches - A and B respectively. In the current settings, if we release a new patch of product A, the next release will be: v0.0.2-a. Then, if we wish to release a new patch for product B, it's version will be v0.0.3-b, our expected behavior is that it will be v0.0.2-b.

Let me know if you think this is an enhancement that can be useful for others as well.

krogon commented 3 months ago

Respecting tag_format fix is available on my fork (v2.3.0 version).