Repository navigation
ci: remove the one-off actions.lock regeneration workflow - #117
hyperpolymath wants to merge 1 commit into
Conversation
#114 landed it on main although it was scratch-only. It fired only on pushes to a deleted branch and its lock has been in main since #116. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
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. |
|
Generated by Claude Code |
|
Add Carrot credits or activate Agent usage billing to use Autofix |
#114 put
.github/workflows/zz-one-off-lock-regen.ymlon main, although it was meant for a scratch branch only. It fires only on pushes to a branch that has since been deleted. The lock it produced reached main in #116, so it has no remaining use.check-lock-sync.shpasses after the removal. The workflow had nouses:, so the lock has no entry to prune.Generated by Claude Code