Fetch tags with --force: the release tag on the server wins
Found in the VM test: when a tag had moved (a re-tagged release), a church's fetch refused it and every later deploy failed its checks. The deploy checks out the tag the Hub asked for, so the remote's tag is the one to trust. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ls1vMdni7EfytGYqQTprME
This commit is contained in:
@@ -56,7 +56,7 @@ status_church() {
|
||||
continue
|
||||
fi
|
||||
if [ "$fetch" = 1 ]; then
|
||||
run_as "$user" "$dir" timeout 20 git fetch --tags --quiet origin 2>/dev/null || true
|
||||
run_as "$user" "$dir" timeout 20 git fetch --tags --force --quiet origin 2>/dev/null || true
|
||||
fi
|
||||
ref="$(checkout_ref "$dir" "$p")"
|
||||
latest="$(latest_tag "$dir" "$p")"
|
||||
|
||||
Reference in New Issue
Block a user