This isn't really correct. Tags don't need to also be paired with a branch. A tag already uniquely identifies a revision.
In the master @ v2.345.6 case, Digger does a calculation in which it takes the date of the tag and finds the closest corresponding commit on another branch. So it's maybe a little deceptive, but very useful if you just want to switch bisect branches.
This isn't really correct. Tags don't need to also be paired with a branch. A tag already uniquely identifies a revision.
In the
master @ v2.345.6
case, Digger does a calculation in which it takes the date of the tag and finds the closest corresponding commit on another branch. So it's maybe a little deceptive, but very useful if you just want to switch bisect branches.