Repository navigation
Restrict cleanup to an explicitly identified test release - #31
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cd081cb0ef
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: df13c52b89
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
The existing cleanup runs on PR closure and branch deletion, passes broad regex/PR matching to a mutable third-party action, and can remove releases unrelated to a controlled publication test. Find Issue Keys additionally deletes workflow history older than seven days.
Replace this with an explicit manual cleanup: require the exact
vMAJOR.MINOR.PATCH-repair.RUN.ATTEMPTtag and full expected commit SHA, resolve its commit, verify that the exact release is a prerelease, then delete only that release ID and tag ref. Preserve production releases and all workflow history. Use the existing GitHub API mechanism through actions/github-script; no additional dependency or custom helper is introduced.Local behavioral verification executes the actual workflow script against a recording API fixture: valid test release deletes exactly one release and tag; production tag, regex input, malformed SHA, mismatched target and stable release all fail before any deletion (6 cases pass). Real controlled-publication cleanup and current-head CI remain to be verified. No production tags or releases were deleted.
Verified completion: latest applicable head passed unit/build/lint and real Jira E2E. Controlled publication run https://github.com/bitflight-devops/github-action-jira-issues-fixversion-manager/actions/runs/38099105448 created an isolated prerelease, uploaded and byte-compared the packaged archive, invoked exact cleanup and verified both tag and release absent. The actual cleanup script also passed 11 local behavioral cases, including partial retries and failure propagation. Merged; subsequent release verification work checks the published main commit.