ci: scope RC release cleanup to its own checkout #50
Labels
No labels
bug
ci
enhancement
feature
privacy
security
theme-system
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/breadbar#50
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?
Child of ECO-28. The current
.forgejo/workflows/rc-release.ymlremoves/tmp/bread-ecosystem-ci-*before creating its own mktemp checkout. That wildcard can delete an active checkout used by a concurrent workflow. Remove the wildcard and retain exact invocation-specific EXIT cleanup. Verify the embedded shell for successful and failing index generation while a sibling active checkout remains intact.PR: #51
The beta index step now uses a prefix older wildcard cleaners cannot match and removes only its own clone via EXIT trap. YAML parsing and the embedded step passed simulated success/failure checks while a legacy-prefix sibling checkout remained intact. Forgejo CI is running; keeping the issue in DOING until it succeeds.
Forgejo CI for PR #51 completed successfully in 5m46s. The PR is ready for independent source review and remains in DOING pending that review.
Reviewed PR #51 against BAR-50:
/tmp/bread-index-XXXXXXdirectory and an EXIT trap removes only that job's directory:.forgejo/workflows/rc-release.yml:53-56./tmp/bread-ecosystem-ci-*prefix, so old cleanup jobs cannot remove it.The PR reports simulated index success and failure checks that preserve a sibling checkout. CI is successful at head
886a439944d6550a3bc001d9a1a0f32dcf81453d, and Forgejo reports the PR mergeable.