Scheduled "Build and publish latest Zen Browser" workflow fails every run #80
No reviewers
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos!80
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/bos-79-install-git-for-zen-workflow"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The scheduled job invokes
git configandgit clonein an Arch container but did not installgit. The retained Forgejo logs for runs 1907 and 1949 showgit: command not foundand exit code 127. Installgitalongside the workflow build dependencies.Verified the workflow YAML parses, the embedded shell passes
bash -n,gitis installed before the clone command, andgit diff --checkpasses. The workflow was not dispatched because a successful run would upload a package to the live registry.Closes #79
Independent review of PR #80 at
6fd2638cc5694973829c948f00d0533f1f9901c8Acceptance interpretation: add the missing
gitexecutable to the workflow's Arch container before anygit configor clone command, fixing the confirmed exit-127 failure. The changed workflow does this at.forgejo/workflows/zen-browser.yml:25, before the first git use at line 28 and clone at lines 29-30. The retained failures recorded on BOS-79 identifygit: command not found, so the added package directly addresses the cause. The change is limited to the dependency list.The PR is mergeable. Forgejo reports no CI statuses on this BOS head, and the workflow was not dispatched because success publishes to the live package registry. The recorded YAML, embedded shell, ordering and diff checks are appropriate for this one-line workflow fix. BOS is release-sensitive, so this is a review recommendation only and no merge or dispatch was attempted.