Revert the CI full-fetch workaround and drop unreachable workflows
CI / lint (push) Failing after 17s
CI / test (push) Successful in 49s
Build op25 / build (push) Successful in 1h29m25s

Shallow clones were never a Gitea packing bug. An intruder had set
uploadpack.packObjectsHook in Gitea's HOME gitconfig, pointing at a
non-executable dropper, so every upload-pack died mid-pack. That hook is
gone and --depth=1 clones are verified working, so fetch-depth: 0 buys
nothing but slower CI. See INCIDENT-2026-08-11.md.

op25-container/.gitea/workflows/* never ran: Gitea only executes
workflows under .gitea/workflows at the repo root, and op25-container is
a subdirectory of this repo, not a repo of its own. The live OP25 image
build is .gitea/workflows/build-op25.yml.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Logan Cusano
2026-08-16 13:00:02 -04:00
co-authored by Claude Opus 5
parent 5ff1089551
commit 9d86304b8a
7 changed files with 0 additions and 167 deletions
-4
View File
@@ -16,11 +16,7 @@ jobs:
env:
CONTAINER_NAME: icecast
steps:
# Full fetch: Gitea fails to pack the default depth=1 shallow clone
# ("bad pack header"). Don't set this back to a shallow fetch.
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: docker/setup-qemu-action@v3