ci: isolate RC release index cleanup #17
Labels
No labels
ci
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/breadclip#17
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-56. The current
.forgejo/workflows/rc-release.ymlremoves/tmp/bread-ecosystem-ci-*before creating its mktemp checkout. That wildcard can delete a sibling workflow's live clone. Replace it with a prefix older workflows cannot match and clean only this invocation's clone on EXIT. Verify successful and failed beta index generation preserve a sibling checkout under the legacy prefix for breadclip.PR: #18
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 simulated success/failure checks passed while a legacy-prefix sibling checkout remained intact. Forgejo CI is running; the issue stays in DOING until it succeeds.
The source change in PR #18 is scoped correctly:
rc-release.yml:55-58uses a unique clone path outside the legacy wildcard prefix and an EXIT trap that removes only this invocation's checkout. The simulated success and failure checks are recorded in the PR description. Current CI for head619857791e111fa1776f78562995acb83dd0426ais still pending (check / check (push)is waiting to run). Leave this issue in TODO until CI finishes, then request independent review again.PR #18 passes local YAML and shell checks plus success/failure cleanup simulations with a legacy-prefix sibling preserved. Forgejo CI was queued at last check. Moving to REVIEW for independent review; if CI fails, return it to TODO with the failure recorded.
Forgejo CI for PR #18 passed in 6m51s on head
619857791e111fa1776f78562995acb83dd0426a. The isolated success/failure cleanup checks and sibling legacy-prefix preservation check pass. The linked PR is ready for the next workflow stage.