3 Commits

Author	SHA1	Message	Date
Niklas Mischkulnig	f51577ae81	ci: Bump withgraphite/graphite-ci-action (#95562) ... - https://github.com/withgraphite/graphite-ci-action/pull/50 - https://github.com/withgraphite/graphite-ci-action/pull/51	2026-07-07 13:26:25 +00:00
Benjamin Woodruff	6f592dec9d	[ci] Disable mid-stack PR optimization for native PR stacks (#95427) ... https://vercel.slack.com/archives/C04KC8A53T7/p1783018076576349 <img width="1015" height="347" alt="Screenshot 2026-07-02 at 11 57 05 AM" src="https://github.com/user-attachments/assets/74d99079-d165-435a-aece-161862795ef6" /> If we're in the middle of a stack, but the PRs below us in the stack are already merged, we should not skip CI jobs. This logic isn't smart enough to handle that.	2026-07-02 19:28:37 +00:00
Benjamin Woodruff	a26a1d640b	[ci] Avoid running full CI mid-stack for GH-native stacks, same as we do for Graphite (#95218) ... Running CI only on the top and bottom of the stack avoids expensive `O(n^2)` behavior when merging one PR at a time and recursively rebasing all the others starting at the bottom of the stack. GitHub added this to the webhook/GH actions object for us to be able to do this: https://vercel.slack.com/archives/C01SKER9S1G/p1777926655162839 Prior to this PR being part of a stack, fails open (runs full CI): <img width="1938" height="993" alt="Screenshot 2026-06-26 at 3 03 37 PM" src="https://github.com/user-attachments/assets/54d6055a-2860-45b3-a03a-a9356b3db2a4" /> Example mid-stack run (skips the full e2e jobs): <img width="1917" height="664" alt="Screenshot 2026-06-26 at 3 24 33 PM" src="https://github.com/user-attachments/assets/9ee466da-f3ea-4298-b5b8-2527d197c121" /> https://github.com/vercel/next.js/actions/runs/28268549361/job/83760907003?pr=95219	2026-07-01 23:22:24 -07:00