Shipfox

Repair failing pull request CI

Get a tested fix when CI fails on a dependency update or an opted-in pull request.

CI fails on a selected GitHub pull request

How it works

  1. CI fails on a selected pull requesttriggerA check fails on a dependency-bot pull request, a labeled pull request, or any same-repository pull request, depending on your choice.
  2. The agent finds the causeagentIt reads the failed logs and the changes in the pull request.
  3. The workflow runs your checks againcheckThe checks confirm that the fix works.
  4. The workflow pushes the fix or proposes itwriteIt pushes one commit to the pull request branch, or it posts a tested patch as a comment.

What it writes

  • GitHub
    • Pushes one commit to the pull request branch, unless it is set to comment only.
    • Comments on the pull request with the result.

Before you start

  • To push fixes, make sure branch rules let the Shipfox app push to the pull request branches.

Choices you make

When you set up this workflow, your coding agent asks you these questions. The workflow file on this page uses the default answers.

  • Which pull requests should the workflow repair?Default: Dependency-bot pull requests2 other choices
    • Dependency-bot pull requestsDefaultRepairs pull requests opened by one dependency bot after its initial CI run fails.
    • Pull requests with a labelRepairs same-repository pull requests that carry a chosen label when CI starts the repair. Anyone who can label a PR opts it in.
    • All same-repository pull requestsRepairs every pull request whose branch lives in the repository, including engineers' branches. Push mode then adds commits to branches people are working on.
  • For dependency-bot pull requests, which bot opens them?Default: Dependabot2 other choices
    • DependabotDefaultRepairs pull requests authored by Dependabot after its initial CI run fails.
    • RenovateRepairs pull requests authored by Renovate after its initial CI run fails.
    • Custom bot loginRequires the exact GitHub login used by the bot.
  • What should the workflow do after the fix passes?Default: Push the fix1 other choice
    • Push the fixDefaultAdds one commit to the pull request branch and posts the result. Existing auto-merge rules can merge the repair, and people working on the branch must pull it.
    • Comment onlyLeaves the branch unchanged and posts a tested patch or an actionable diagnosis.

Models

  • fixtested with gpt-6-sol · high thinkingReads failed CI logs and repairs the pull request branch.

When you set up this workflow, your coding agent suggests models that your workspace can use. You choose the model for each step.

Related examples

Was this page helpful?
Edit this page on GitHub