CI: isolate beta and stable index generation clones #20
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?
The release workflows still clean a runner-wide shared path before cloning bread-ecosystem. In rc-release.yml the
rm -rf /tmp/bread-ecosystem-ci-*glob can delete another concurrent job's mktemp clone. In release.yml the fixed/tmp/bread-ecosystem-cipath has the same collision risk. Give each invocation its own mktemp directory and clean only that directory. Keep the change limited to these workflows.Implemented in breadcrumbs PR #21. The beta and stable workflows now clone into job-unique mktemp directories and remove only their own clones. YAML parsing, shell syntax, and diff checks pass.
Review: implementation matches the requested scope. Acceptance criteria: (1) beta clone must use a job-unique temporary directory and avoid deleting other jobs' directories, satisfied by
.forgejo/workflows/rc-release.yml:54-57; (2) stable clone must use a job-unique temporary directory and clean only its own clone, satisfied by.forgejo/workflows/release.yml:58-61. No unrelated workflow files changed. I found no code changes to request. PR #21 is mergeable, but itscheck / check (push)CI status is still pending, so this is not a merge approval yet. I am leaving the issue in REVIEW pending CI.