3 ms·
Learning question: so the tag was on an orphaned commit? What ways could this be resolved? The obvious and chosen one was to tag a new release and explain to p
by RubyPinch 10y ago
Learning question:
so the tag was on an orphaned commit? What ways could this be resolved?
The obvious and chosen one was to tag a new release and explain to people that the old one isn't accessible because of a muck up.
Would of merging it back in worked? that would of fixed the "<nwc10> the tag is for a commit which is not a parent of nqp master" right?
- _ikke_ 10y agoThe commit is not orphaned, because the tag is still pointing to it, but it's indeed not reachable from a branch anymore. git does not update local tags when the tag has changed remotely (see "on retagging" in the git tag man-page), so it would have to be a different tag. Merging it back would be confusing, because you know have the old branch and the new branch in your history. It would cause the tag to be reachable again from master though.