pr-green-loop

You can automatically fix failing CI checks on a GitHub pull request by running an iterative loop that pushes your branch, waits for checks to complete, diagnoses failures, applies fixes, and re-pushes until the PR is green.

Yes, you need the gh CLI installed and authenticated to automate PR CI fixes. This workflow requires a remote-tracking GitHub pull request and relies on the gh CLI to interact with checks and push updates.

The automated CI remediation loop handles Bugbot findings by incorporating them into the iteration cycle. It diagnoses both CI check failures and Bugbot findings, applies necessary remediation, and re-pushes the branch to verify all issues are resolved.

The best way to iterate CI fixes and re-pushes until a PR turns green is to delegate the diagnosis and fix application to specialized skills. This loop repeatedly pushes updates, waits for CI completion, and applies fixes until all checks pass.

Yes, you can remediate Bugbot findings and CI failures across multiple iterations. The loop repeatedly checks the pull request status, applies fixes for both CI failures and Bugbot findings, and re-pushes until the PR successfully turns green.

Your automated pull request loop requires a remote-tracking PR because it needs to monitor and interact with existing GitHub CI checks. Without a remote-tracking PR, the iterative loop cannot wait for checks to complete or push updates to drive the CI status to green.