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

supabase / cli / 38925127345
67%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 16 Oct 2026 03:36PM 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

16 Oct 2026 03:34PM UTC coverage: 66.737%. Remained the same
38925127345

push

github

web-flow
ci(release): re-review repaired syncs and re-resolve them when next moves (#7205)

## Summary

**TL;DR:** Since #7124, no Claude-resolved `sync/develop-into-next` PR
has been auto-approved by `supabase-oss`. Claude's repair commit moves
the head past the only AI review, so the approval gate (review head must
equal PR head) never passes. This adds one bounded AI re-review after a
repair, and when `next` moves and conflicts at fast-forward time, Claude
re-resolves the same PR instead of asking a maintainer.

**Before**

```mermaid
flowchart LR
  A[AI review on X] --> B[Claude repair pushes Y]
  B --> C{"review head == Y?"}
  C -- no --> D[skip forever]
  D --> E[human approves]
  F[next moved + conflict] --> G[ask human to resolve]
```

**After**

```mermaid
flowchart LR
  A[AI review on X] --> B[Claude repair pushes Y]
  B --> C[one AI re-review on Y]
  C -- "clean or all answered" --> D[supabase-oss approves]
  C -- "needs a fix / CI red" --> E[maintainer]
  F[next moved + conflict] --> G["Claude re-resolves same PR<br/>(max 2 resyncs)"]
  G --> A
```

### Why

On #7158, the AI review saw `39034946` and the repair pushed `b064c720`.
Every later `sync-repair` run then logged "Nothing to repair; the AI
review did not see this head." until a maintainer approved it. On #7112,
`next` moved after approval and the resync conflicted, which left the PR
waiting on a person.

### What changed

- A resolution is everything after the latest resolve comment (from the
first Claude resolve or a resync). Repair rounds count per resolution,
using release-bot comments and reviews sorted by time.
- After a repair push, `sync-repair` posts a re-review marker, and a
separate `actions: write` job dispatches the AI review once. The job
that runs Claude never gets that permission. If the dispatch fails, it
tags maintainers.
- After the re-review, rounds can only reply to findings. Claude
declines repeats by pointing at its earlier replies. If a finding needs
a fix or CI fails... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38925127345.1 16 Oct 2026 03:36PM UTC 79
66.74
GitHub Action Run
Source Files on build 38925127345
  • 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 #38925127345
  • f01410ec on github
  • Prev Build on develop (#38918479241)
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