Use a full fetch in CI: Gitea fails to pack a shallow clone
Build & Deploy / Build & push images (push) Failing after 50s
Build & Deploy / Deploy to VM (push) Has been skipped

actions/checkout defaults to depth=1, and Gitea aborted generating that pack
with a bad pack header protocol error on all three retries, failing the build
before any image was pushed. A full fetch avoids the shallow-pack path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Logan Cusano
2026-08-16 10:09:06 -04:00
co-authored by Claude Opus 5
parent 052dda0b1f
commit 518ac46929
+6
View File
@@ -14,7 +14,13 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
# fetch-depth: 0 on purpose. The default depth=1 shallow fetch made Gitea
# die generating the pack ("fatal: protocol error: bad pack header",
# retried three times and failed the run). A full fetch takes the slow
# path on the server and works. Don't "optimise" this back to depth=1.
- uses: actions/checkout@v4 - uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Set up Docker Buildx - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3 uses: docker/setup-buildx-action@v3