ci(build-linux): use manual git clone for checkout (Forgejo auth bug) #9

Merged
mik-tf merged 1 commit from development_mik_d05_checkout_manualclone into development 2026-05-05 12:59:00 +00:00
Owner

v0.1.0-rc4 release workflow (run #74) failed on both matrix legs at the Checkout step with:

fatal: could not read Username for https://forge.ourworld.tf: terminal prompts disabled

actions/checkout@v4 has a known auth bug against forge.ourworld.tf — the FORGEJO_TOKEN reaches the workflow and the extraheader is configured, but the underlying git fetch ignores it. Editors own build.yaml (the test CI) already documents this and uses a manual git clone workaround.

This ports the same workaround to build-linux.yaml. Tag-triggered: $GITHUB_REF_NAME is the tag, and git clone --branch accepts both tags and branches so the same command works for workflow_dispatch too.

After merge: delete + re-push tag v0.1.0-rc4 to unblock session 60.

v0.1.0-rc4 release workflow ([run #74](https://forge.ourworld.tf/lhumina_code/hero_editor/actions/runs/74)) failed on both matrix legs at the Checkout step with: ``` fatal: could not read Username for https://forge.ourworld.tf: terminal prompts disabled ``` actions/checkout@v4 has a known auth bug against forge.ourworld.tf — the FORGEJO_TOKEN reaches the workflow and the extraheader is configured, but the underlying `git fetch` ignores it. Editors own `build.yaml` (the test CI) already documents this and uses a manual `git clone` workaround. This ports the same workaround to `build-linux.yaml`. Tag-triggered: `$GITHUB_REF_NAME` is the tag, and `git clone --branch` accepts both tags and branches so the same command works for `workflow_dispatch` too. After merge: delete + re-push tag `v0.1.0-rc4` to unblock session 60.
ci(build-linux): use manual git clone for checkout (Forgejo auth bug)
All checks were successful
Build and Test / build (pull_request) Successful in 14m47s
9693435308
actions/checkout@v4 fails on forge.ourworld.tf with "could not read
Username for 'https://forge.ourworld.tf'" — the FORGEJO_TOKEN reaches
the workflow and the extraheader gets configured, but the underlying
git fetch ignores it and falls back to a TTY prompt.

v0.1.0-rc4 hit this on both matrix legs (run #74). Editor's existing
build.yaml has documented this exact bug since PR #4 and works around
it with a manual clone — same pattern needs to land in build-linux.yaml.

Tag-triggered builds: $GITHUB_REF_NAME is the tag name (e.g. v0.1.0-rc4)
and `git clone --branch` accepts both branches and tags, so the same
clone command works for the workflow_dispatch path too.

After this lands, re-tag v0.1.0-rc4 (delete + re-create) to unblock
session 60. The producer PR (#8) doesn't need to be reopened.

Signed-off-by: mik-tf
mik-tf merged commit 88d4e55609 into development 2026-05-05 12:59:00 +00:00
mik-tf deleted branch development_mik_d05_checkout_manualclone 2026-05-05 12:59:01 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_editor!9
No description provided.