• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 38382577616
67%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 13 Oct 2026 10:20AM UTC
Jobs 1
Files 79
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

13 Oct 2026 10:19AM UTC coverage: 66.737%. Remained the same
38382577616

push

github

web-flow
ci(release): resolve and repair develop-into-next syncs with Claude (#7083)

## TL;DR

`next` now catches up with `develop` without a maintainer hand-resolving
every conflict. When a push to `develop` conflicts with `next`, Claude
resolves the existing sync PR, and once CI and the AI review finish it
fixes what the merge broke and answers the review. Landing on `next`
still needs a maintainer's approval.

## Before

```mermaid
flowchart LR
  push["push to develop"] --> merge{"merge into next"}
  merge -->|clean| next[("next")]
  merge -->|conflict| pr["sync PR<br/>(develop tip)"]
  pr --> human["maintainer merges next,<br/>resolves, pushes"]
  human --> approve["approve"] --> next
```

## After

```mermaid
flowchart LR
  push["push to develop"] --> merge{"merge into next"}
  merge -->|clean| next[("next")]
  merge -->|conflict| pr["sync PR<br/>(develop tip)"]
  pr --> claude["Claude resolves,<br/>push + AI review"]
  claude --> settle{"CI + review done"}
  settle -->|"failures or findings"| repair["Claude repair round<br/>(max 2)"] --> settle
  settle -->|green| approve["approve"] --> next
  repair -->|"limit hit"| ping["ping @supabase/cli"]
  claude -->|"cannot resolve"| human["maintainer resolves"]
```

## Why

Every `develop` → `next` conflict waited for a maintainer to merge,
resolve, and push by hand, and later syncs skipped while the PR stayed
open, so `next` drifted further behind each day.

## What changed

- **Resolve** (`Sync branches`): after a `develop-into-next` conflict PR
opens, Claude merges `next` into the sync branch with file read, search,
and edit tools only: no shell, no web tools, no `.git` edits, and no
GitHub token. It is asked to update every remaining use of anything one
side renamed or removed, including files that did not conflict, and
keeps `next`'s `pnpm-lock.yaml` for regeneration. A second job with no
secrets formats the tree, regenerates the lockfile, and runs `check:all`
and unit tests; a third lets Claude fix what fa... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38382577616.1 13 Oct 2026 10:20AM UTC 79
66.74
GitHub Action Run
Source Files on build 38382577616
  • Tree
  • List 79
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #38382577616
  • 0f1a103b on github
  • Prev Build on gh-readonly-queue/develop/pr-7108-4d331f104ead26256f4f7664dec1cbcda1230be2 (#38380924328)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc