Active Branch Tag Traversal for Merge Commits

[nesselrathSemvox]

When searching for version tags in a Git repository, the poetry-dynamic-versioning plugin should optionally follow only the currently active branch when traversing merge commits. In the case of a merge commit, the plugin should ignore tags that are reachable exclusively through other branches and continue traversal strictly along the history of the checked-out (active) branch. This ensures that version tags reflect the linear history of the current branch and do not include tags from branches that have been merged.

[mtkennerly]

Hi! Sorry for the late reply here 😅

Strictly speaking, tags apply to commits, not to branches. If you merge a tagged commit into the current branch, and that commit retains its tag, then the plugin would consider that to have become part of the current branch.

So I can understand your use case better, could you give me a more concrete example of your workflow and what kinds of tags you're creating in other branches that you don't want reflected in the current branch?

[nesselrathSemvox]

Thank you, you are absolutely right. In the meantime I have dug a littler bit deeper into this topic and this feature request makes no real sense anymore. For my use-case I found a custom solution where I select the highest version from the overall history from all branches. The main problem was that from merged branches sometimes a tag from newer commits with lower version number (e.g. 1.1.1 from a patch release branch) was used instead of the version number of my main branch with the development of new features (e.g. 2.0.0).

Maybe this could be an interesting configuration option for your plugin?