When we run git fetch without a specific revision we usually run it with --all which fetches tags (among other things).
We now have movable tags in our plugin repositories and when a tag is moved a git fetch or checkout will produce a 'would clobber existing tag' error on the command line, which warns the user that the tag that has already been checked into the local clone will be overwritten.
This commit fixes that error by running fetch with --force if we do not specify a revision.
Testing
This can only be tested if you have a repo checked out with a major revision tag of a plugin which has been moved, in which case you will see would clobber existing tag when you run whippet deps update. At this point, you can try the same thing with this branch and see if that fixes the issue.
Merge checklist
[ ] Includes tests (if new features are introduced)
[ ] Commit message includes link to the ticket/issue
[x] Changelog updated
[x] PR open against dxw's Homebrew Tap to point the Whippet formula to the new version number
When we run
git fetchwithout a specific revision we usually run it with--allwhich fetches tags (among other things).We now have movable tags in our plugin repositories and when a tag is moved a
git fetchorcheckoutwill produce a 'would clobber existing tag' error on the command line, which warns the user that the tag that has already been checked into the local clone will be overwritten.This commit fixes that error by running
fetchwith--forceif we do not specify a revision.Testing
This can only be tested if you have a repo checked out with a major revision tag of a plugin which has been moved, in which case you will see
would clobber existing tagwhen you runwhippet deps update. At this point, you can try the same thing with this branch and see if that fixes the issue.Merge checklist