Paul Hatcherian
Paul Hatcherian
With `version_from_branch` set to `true`, if you are on branch `release/11.2` the version should always be `11.2.*`. There is a method called `ResolveBranchNameAsync` which should call `git rev-parse --abbrev-ref HEAD`...
@ThomasDahll What does the URL for enterprise deployments look like? Perhaps just making this a relative URL would be enough.
It should not be doing this, thanks for reporting.
By automatically tagging each commit with the version, you are causing the version to be incremented on the next commit.
Hey Naveen, thanks and glad you find it useful. So I think what you're saying is that you want the behavior of bump each commit, but only for cases when...
There is not currently a way to do this (aside from using tags/branches with the normal flow). It could be added. I worry about adding a "patch_pattern" type input to...
This is the "normal" mode of operation for this action. On each run this action is predicting what the version will be for the target commit if it were released....
Now available in v5.1.0
Hello Manuel, Yes, this can be accommodated. So looking at the current "pipeline" there are several steps, for example: - Determine the last commit that was released - Determine the...
See release of [version 5.0.0](#47), I have been playing with a `BranchLastReleaseResolver` implementation to enable this feature, but there are some issues with this strategy. If the version branch falls...