Repository navigation
ci: retire auto-merge workflow - #51
Conversation
Active development is cooling off and Qodo covers review, so the unattended-merge path is no longer worth a standing pull_request_target workflow with a write token. Required checks still gate every merge - they now just need a click.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smith-xyz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
PR Summary by QodoRetire the auto-merge workflow
AI Description
Diagram
High-Level Assessment
Files changed (1)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewPowered by Qodo |
What
.github/workflows/auto-merge.yml— thepull_request_targetworkflow that armed GitHub's native auto-merge (theautomergelabel or a ticked test checkbox) so green PRs landed without a clickWhy
Active development is cooling off and Qodo now handles code review, so the unattended-merge path is no longer worth a standing privileged trigger with a write token. Required checks still gate every merge — merging just needs a click again.
Notes