bread-ecosystem main-trigger workflows still clone into shared src #81
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Found during ECO-79 follow-up review of bread-ecosystem workflows.
.forgejo/workflows/dev-bakery.yml,dev-bread-theme.yml, andpackage.ymlstill use the shared relativesrccheckout path. This is separate from the isolated check workflow changed by ECO-79 PR #79.Confidence: high that these files retain the fixed-path checkout pattern by source inspection. No failure in these workflows is attributed to a runner interleaving; the exact shared workspace behavior is not confirmed from the runner.
After the shared checkout helper is reviewed and merged, update only these main-trigger workflows in a separate fix branch/PR: acquire a pinned helper revision, verify its committed SHA-256 before use, check out the event SHA into a per-job directory, export the directory through GITHUB_ENV, and clean only that invocation's directory in a final always step. Preserve package/artifact paths and verify their consumers.
Regression: local workflow fixture for exact-SHA and directory isolation, plus relevant CI checks. Do not batch other repositories or the rc/stable workflows here.
PR open: #85 (fix/eco-82-main-trigger-checkout). Head SHA:
848cfb0481. dev-bakery.yml and dev-bread-theme.yml moved to the per-job checkout; package.yml now checks out GITHUB_SHA with the same verification (its path is already per-job in the Arch container). Verified: YAML parses, bash -n on all run blocks, grep for leftover src refs, local fixture of the checkout/cleanup blocks (exact SHA, concurrent jobs isolated, cleanup scoped, non-SHA rejected). Not run: the main-trigger and tag workflows on the runner, and any publish. Pinned-helper follow-up not done; inline bootstrap used as in check.yml.