-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
I don't have a repro on hand, so this is more of just a fyi / something to keep an eye out for.
I'm pretty sure its related to merging a branch (say featureA) into master where featureA has had master and other branches merged into it several times. Once master is in the 'bad state', gogitver will return one of several different version numbers when run consecutive times on the same git repo. If I had to guess, its related to an unstable sort somewhere.. but I really have no idea ; ).
The workaround is to tag ahead of the current version range.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels