You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case of merge commits, what-bump always follows the first parent, which happens to be the main branch. This breaks when the release tag is on a separate branch: in this case what-bump will follow all commits on the main branch `til the root is found, then stops.
Ideally, what-bump should do what git does, and properly find a path from HEAD up to the revision specified on the command-line. However, I have no idea how to achieve this.
If multiple paths exist from HEAD to the target revision, then some way to disambiguate would be desirable (even though either erroring out or choosing an arbitrary path by default would be OK).
The text was updated successfully, but these errors were encountered:
In case of merge commits,
what-bump
always follows the first parent, which happens to be the main branch. This breaks when the release tag is on a separate branch: in this case what-bump will follow all commits on the main branch `til the root is found, then stops.Ideally, what-bump should do what git does, and properly find a path from HEAD up to the revision specified on the command-line. However, I have no idea how to achieve this.
If multiple paths exist from HEAD to the target revision, then some way to disambiguate would be desirable (even though either erroring out or choosing an arbitrary path by default would be OK).
The text was updated successfully, but these errors were encountered: