ci: gate main-targeted PRs on human authorship too - #2840
Conversation
The human-authors job only exists on dev, so every PR based on main runs without it. That is how aa6db97 (`chore: retrigger OTA build`, empty, authored by chip-peanut-bot) reached main through #2823 — and once on main it can never be rewritten, which is what left the back-merge #2830 stuck. Same job, same script as dev after #2839, byte-identical so the next dev -> main release merges it without a conflict. Wired into ci-success so it actually gates.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
On-demand reviews are free for the next 25 days. After that, they cost $0.25 per reviewed file. Or wait 11 minutes for your next included review. View limit detailsLimit details: You’ve used the included review currently available. Your 60 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Comment |
|
Same Dependabot caveat as peanut-api-ts#1436: there is no |
Code-analysis diffPainscore total: 7349.95 → 7349.95 (0) |
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
Why
human-authorswas added ondevand has not reachedmainyet, so every PR based onmainruns without it. That is not a theoretical gap — it is exactly how the current mess happened:main) carriedaa6db97—chore: retrigger OTA build, an empty commit authored bychip-peanut-bot[bot]. Ungated, so it merged.aa6db97is now an ancestor ofmainand can never be rewritten (non_fast_forward+required_signaturesonrefs/heads/**, zero bypass actors).What
The same job, with the same script as
devhas after #2839 — byte-identical text in the same position, so the nextdev→mainrelease merges it as the same change rather than a conflict. Added toci-success.needsso it actually gates.Effect on open
mainPRsI checked every one. Only #2829 fails: its single commit
4d393a7is authored bychip-peanut-bot[bot]. That is the gate doing its job — the fix is to re-commit that one-line change from a human account. Everything else (#2833, #2835, #2836) is human-authored and unaffected.The content pipeline is unaffected:
update-content.ymlcommits asHugo Montenegro <h@hugomontenegro.com>, a real account, so content-publish PRs pass and merge-on-green keeps working.Depends on nothing — but merge #2839 first if you want the two files to converge cleanly.