Fix failing dependency-bot CI
Get a tested fix for every dependency update that breaks CI.
CI fails on a dependency-bot pull request
How it works
- A dependency update fails CItriggerDependabot or Renovate opens a pull request, and a check fails.
- The agent finds the causeagentIt reads the failed logs and the changes in the update.
- The workflow runs your checks againcheckThe checks confirm that the fix works.
- The workflow pushes the fix or proposes itwriteIt pushes to the branch of the bot, or it posts a patch as a comment.
What it writes
- GitHub
- Pushes to the bot branch or comments with a patch
Before you start
- Connect GitHub.
- Run CI on GitHub Actions, with Dependabot or Renovate opening update pull requests.
- To push fixes, let the Shipfox app commit to the branches of the bot.
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 dependency bot opens update pull requests?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 fixDefaultUpdates the bot branch and posts the result. Existing auto-merge rules can merge the repair.
- 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 dependency update 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