Unverified Commit 10c5a6ac authored by Tobias Koppers's avatar Tobias Koppers Committed by GitHub

Sequence CI for branch-based PR stacks (#99086)

### What?

Replace the Graphite-specific CI optimizer with a **read-only TypeScript
gate** for PR stacks formed by ordinary GitHub base/head branch links.
This PR includes the work previously reviewed in #99116 and #99122.

### Why?

Rebasing a large stack starts expensive `build_and_test` jobs on every
PR at once. Let the first three PRs and the top PR run immediately, but
defer middle PRs until nearby CI provides a useful signal. A deferred PR
must **not** appear mergeable just because its jobs have not started.

### How?

- **Find the stack from branch relationships**, not GitHub stack
metadata. Middle PRs poll their three nearest predecessors every **five
minutes**. Any predecessor with a successful, current-head/current-base
`thank you, next` check releases full CI; three unsuccessful results
**fail the gate and required aggregate**. While waiting, the gate stays
in progress. After five hours without a decision, it releases full CI
rather than stranding the PR.
- **Revalidate before deciding.** Refresh PR and check data before
release/failure so rebases, retargeting and reruns cannot make a stale
check decisive. Transient GitHub 5xx/429 errors retry; permanent errors
or ambiguous topology start full CI rather than claiming CI passed.
- **Keep polling cheap and read-only.** Reuse PR head/base data from
`pulls.list` (11 → **8 REST reads** per ordinary waiting poll), while
still checking *all three* predecessors. The bundled action is checked
out at the current test-merge `${{ github.sha }}` without persisted
credentials; forks bypass the checkout/gate and run full CI. The
six-hour gate stays on `ubuntu-latest` because `ubuntu-slim` has a
15-minute limit.

<details>
<summary>Implementation and review tradeoffs</summary>

- The local action bundles a pinned Octokit. Isolated Jest tests use
fake timers and a real check-run response fixture. CI runs the existing
Next.js lint/examples/externals/browser checks before action-specific
install, typecheck, build and Jest; a generated-diff guard catches stale
bundles.
- `uses: ./...` requires action files already in the job workspace; it
does not fetch them like `owner/repo@ref`. The sparse checkout fetches
only `action.yml` and `dist/index.js`. Caller and reusable workflow
grant read-only `checks`, `contents` and `pull-requests` permissions;
the gate inherits no secrets.
- Cheap-check graph splitting was deliberately deferred. Job-level
concurrency does not enforce predecessor *success*; stopping at the
first pending predecessor misses an older success. GraphQL batching
needs a verified check-association projection and measured cost before
replacing the current REST lookup.
- When the child commits became reachable from this branch, GitHub
automatically marked #99116 and #99122 merged; no PR merge operation was
used. [Action
README](https://github.com/vercel/next.js/blob/ci/branch-stack-polling-gate/.github/actions/pr-stack-ci-gate/README.md)
documents the contract.

</details>

### Verification

- **Focused checks:** TypeScript, Prettier, deterministic bundle/diff
checks and **24/24 Jest** passed. The final comment-only change in
`src/gate.ts` produced a byte-identical bundle. The [current root
run](https://github.com/vercel/next.js/actions/runs/35967795126) passed
its gate, lint and required `thank you, next` on **attempt 2** (same
SHA); attempt 1 failed an intermittent redbox test.
- **Live six-PR test on the compiled action:** the first three and top
passed the gate immediately. Middle #99097 and #99098 **waited**. On
initial attempts, both **failed closed** when their three predecessors
were unsuccessful, with no expensive jobs started. On rerun, #99097
**released on #99086's success** despite #99096 failing and #99095 still
pending; full CI ran but failed unrelated tests. #99098 waited for *its
own* three predecessors, then failed closed again. Gate release never
marked full CI successful.
- **Known limitation:** product-test failures—not the gate—left four
immediate/released PRs with failed full CI on various attempts. All five
test drafts remain open for reuse. Workflow reruns in this experiment
were initiated externally; this agent's GitHub integration received 403
(`actions=write` required) when attempting a rerun.

<details>
<summary>Current compiled-action six-PR results, with workflow and gate
logs (2026-09-24)</summary>

Each draft is one Jest assertion commit over its signed parent; the
cumulative focused suite passes **24/24**. Times below are UTC.
“Required” refers to `thank you, next`, not the gate check.

| Position | PR / signed head / workflow | Gate outcome | Required check
| Expensive work |
| :-- | :-- | :-- | :-- | :-- |
| 1 |
[#99086](https://github.com/vercel/next.js/actions/runs/35967795126)
`85444c9e` | immediate pass | failed attempt 1; **passed attempt 2** |
ran twice |
| 2 |
[#99095](https://github.com/vercel/next.js/actions/runs/35969902709)
`bc19787a` | immediate pass | failed attempts 1 and 2 | ran twice |
| 3 |
[#99096](https://github.com/vercel/next.js/actions/runs/35970016367)
`98bfab58` | immediate pass | failed | ran |
| 4 |
[#99097](https://github.com/vercel/next.js/actions/runs/35970109573)
`e260bf96` | [attempt
1](https://github.com/vercel/next.js/actions/runs/35970109573/job/107537584401):
waited → failed 08:02; [attempt
2](https://github.com/vercel/next.js/actions/runs/35970109573/job/107609256427):
**released 11:19** | failed both attempts (attempt 2: product tests) |
none on attempt 1; full CI ran on attempt 2 |
| 5 |
[#99098](https://github.com/vercel/next.js/actions/runs/35970206069)
`01222d4a` | [attempt
1](https://github.com/vercel/next.js/actions/runs/35970206069/job/107537887530):
waited → failed 08:03; [attempt
2](https://github.com/vercel/next.js/actions/runs/35970206069/job/107609367420):
waited → failed 11:50 | failed both attempts | **never started** |
| 6 (top) |
[#99099](https://github.com/vercel/next.js/actions/runs/35970312588)
`c6f3cf4a` | immediate pass | failed attempts 1 and 2 | ran twice |

**Decision evidence:** On attempt 1, #99097 saw #99096/#99095/#99086 all
unsuccessful, and #99098 saw #99097/#99096/#99095 all unsuccessful;
their required checks failed and downstream jobs were skipped *because
their gates failed*. After #99086's successful rerun, #99097 attempt 2
logged `#99096=unsuccessful, #99095=waiting, #99086=success`; its gate
passed and [build-next actually ran and
passed](https://github.com/vercel/next.js/actions/runs/35970109573/job/107609336752).
#99098 could not use #99086 (outside its nearest-three window); it
failed at 11:50 when #99097/#99096/#99095 had all finished without
success. Completed failed gates do not restart automatically when a
predecessor reruns.

</details>

<details>
<summary>Unrelated CI failures and recovered flaky tests</summary>

- #99086's attempt 1 failed `lazy-dynamic-imports › does not parse a
dynamic import target before activation`: redbox source was `null` after
all in-job retries
([job](https://github.com/vercel/next.js/actions/runs/35967795126/job/107530613870)).
**The same-head workflow passed on attempt 2.**
- #99095, #99096, #99097 attempt 2 and #99099 failed
`instant-insights-tab-overlay › should wrap the mobile overlay header
only when it does not fit`: observed header top difference **24**,
expected **< 4**, after in-job retries ([example
job](https://github.com/vercel/next.js/actions/runs/35969902709/job/107537341995)).
#99096 also failed `turbopack-loader-file-dependencies › should update
when a build dependency changes` (`build-one` instead of `build-two`,
[job](https://github.com/vercel/next.js/actions/runs/35970016367/job/107537932737)).
#99097 attempt 2 additionally failed the `lazy-dynamic-imports` redbox
assertion in an experimental cache-components shard
([job](https://github.com/vercel/next.js/actions/runs/35970109573/job/107609732882)).
These failures are not gate-test failures.
- **Recovered in-job flakes:** #99096
`instant-validation/head-and-reporting › invalid - runtime prefetch -
dynamic viewport blocks navigation` (redbox did not open; passed retry
1/2); #99095 `use-cache-without-experimental-flag › should recover from
the build error if useCache flag is set` (Playwright execution context
destroyed on navigation; passed retry 1/2); #99097 attempt 2
`lazy-dynamic-imports` in a different Turbopack-dev shard (passed retry
2/2), `instant-validation/suspense-boundaries` (redbox did not open;
passed retry 2/2), and
`instant-validation/head-and-reporting.partial-prefetching` (redbox did
not open; passed retry 1/2).

</details>

<details>
<summary>Earlier implementation smoke tests and CJS-gate stack
runs</summary>

- The [folded-code root head `89f0ca34` full
run](https://github.com/vercel/next.js/actions/runs/35965443069) passed
gate, build, lint (including **24/24 Jest**) and required `thank you,
next`. The earlier [compiled-action child head `25647f00`
run](https://github.com/vercel/next.js/actions/runs/35922700289) also
passed full CI, proving same-SHA sparse checkout before the lint-order
follow-up was folded into root.
- **CJS-gate fail-closed run (base `ec0abf41`, 2026-09-23):**
[#99086](https://github.com/vercel/next.js/actions/runs/35875541530),
[#99095](https://github.com/vercel/next.js/actions/runs/35875598833),
[#99096](https://github.com/vercel/next.js/actions/runs/35875651890) and
top [#99099](https://github.com/vercel/next.js/actions/runs/35875952426)
ran full CI and failed unrelated tests. Middle
[#99097](https://github.com/vercel/next.js/actions/runs/35875701404/job/107231099534)
failed its gate at 15:20 and
[#99098](https://github.com/vercel/next.js/actions/runs/35875873698/job/107231827956)
at 15:21; required checks failed and expensive jobs never started. A
Turbopack source-map snapshot failure was subsequently fixed in
[#99106](https://github.com/vercel/next.js/pull/99106).
- **CJS-gate release run (base `8ff7f2bd`, 2026-09-23):**
[#99086](https://github.com/vercel/next.js/actions/runs/35887913444) and
[#99095](https://github.com/vercel/next.js/actions/runs/35887957948)
passed full CI.
[#99097](https://github.com/vercel/next.js/actions/runs/35888074168/job/107273254039)
and
[#99098](https://github.com/vercel/next.js/actions/runs/35888146874/job/107273514756)
waited, then released at the next poll on #99095's green check while a
nearer predecessor was unresolved. Their later full CI failed; top
[#99099](https://github.com/vercel/next.js/actions/runs/35888202575)
started immediately (later canceled). These precede the TypeScript
action and are not claimed as evidence for its current head.

</details>

<!-- NEXT_JS_LLM -->


<!-- fleet d2ae64f1-7106-4ba4-b88a-7785c19904c6 -->

---------
Co-authored-by: 's avatarvercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
Co-authored-by: 's avatarTobias Koppers <1365881+sokra@users.noreply.github.com>
parent 34fdbdcc
# PR Stack CI Gate
The `build_and_test` workflow calls this read-only action for same-repository PRs.
It infers branch-based stacks from open PR head/base branch names; no GitHub
stack API or Graphite integration is required. Fork PRs bypass the checkout and
this action entirely and run full CI immediately.
The first three PRs and every leaf run immediately. An internal PR polls the
closest three predecessors every five minutes: **any** current-head/current-base
`thank you, next` success releases full CI, while three terminal failures fail
the required gate. Unresolved waits open after five hours (six-hour job timeout).
Transient GitHub 5xx/429 errors retry every five minutes; other errors start
full CI so they cannot accidentally mark the aggregate green.
## Development
```bash
pnpm --dir .github/actions/pr-stack-ci-gate install --frozen-lockfile --ignore-scripts
pnpm --dir .github/actions/pr-stack-ci-gate types
pnpm --dir .github/actions/pr-stack-ci-gate build
pnpm --dir .github/actions/pr-stack-ci-gate test
```
Commit changes to `src/` **and** the generated `dist/index.js` and
`dist/licenses.txt`. Tests use an isolated Jest config because the repository's
main Jest config searches only the `test/` and package trees. A captured shape
from #99095's actual required-check response lives in `fixtures/`. The workflow
sparse-checks out only `action.yml` and `dist/index.js` from `${{ github.sha }}`;
that is the test-merge commit on PR runs. The caller and action job grant only
`checks: read`, `contents: read` and `pull-requests: read`. No secrets are
inherited, and `persist-credentials` is false.
## API budget and correctness
A stable middle-PR poll rechecks its own PR, finds successors, walks three
predecessor links and checks all three required results: **8 REST calls** versus
11 before this action. The `pulls.list` response already contains head/base
SHAs, so the three extra predecessor `pulls.get` calls are unnecessary while
waiting. Before opening or failing, the action re-reads current PR metadata and
the decisive predecessor(s) and check(s). We cannot stop at the first pending
predecessor: an older PR can already have passed; nor can we permanently cache
a terminal failure because that PR can succeed on rerun. Rechecking live branch
topology on *every* five-minute poll catches retargeted, closed, or leaf PRs at
the original cadence.
GitHub's `GITHUB_TOKEN` primary budget is typically **1,000/hour/repository**
for both REST requests and GraphQL points. Most REST GETs cost one point.
GraphQL may batch data into a one-point query, but the check-run-to-PR base-SHA
association and nested pagination would need independent correctness testing;
this implementation instead takes a measured REST reduction without weakening
the already verified current-base guard. An `ubuntu-slim` runner is unsuitable:
its 15-minute job limit is shorter than the gate's multi-hour wait.
name: 'PR Stack CI Gate'
description: 'Delay expensive CI for branch-based stacked pull requests until prior CI succeeds.'
runs:
using: 'node24'
main: 'dist/index.js'
This diff is collapsed.
This diff is collapsed.
{
"id": 107285638067,
"name": "thank you, next",
"status": "completed",
"conclusion": "success",
"head_sha": "360b493601939d820d35a77c2d4ec691ce12089d",
"html_url": "https://github.com/vercel/next.js/actions/runs/35887957948/job/107285638067",
"app": { "slug": "github-actions" },
"pull_requests": [
{
"number": 99095,
"head": { "sha": "360b493601939d820d35a77c2d4ec691ce12089d" },
"base": {
"ref": "ci/branch-stack-polling-gate",
"sha": "939d61265dcb4a6f91485eb08b0907062f71ab51"
}
}
]
}
This diff is collapsed.
const ts = require('typescript')
// Jest runs the TypeScript action source without emitting temporary JS into
// the repository checkout (where repo-wide lint would discover it).
module.exports = {
process(source, filename) {
return {
code: ts.transpileModule(source, {
fileName: filename,
compilerOptions: {
module: ts.ModuleKind.CommonJS,
target: ts.ScriptTarget.ES2024,
esModuleInterop: true,
},
}).outputText,
}
},
}
module.exports = {
rootDir: __dirname,
testEnvironment: 'node',
testMatch: ['<rootDir>/**/*.test.js'],
transform: { '^.+\\.ts$': '<rootDir>/jest-typescript-transform.cjs' },
clearMocks: true,
}
{
"private": true,
"description": "Read-only CI gate for branch-based pull request stacks",
"scripts": {
"build": "ncc build src/index.ts -m -o dist --license licenses.txt",
"types": "tsc --noEmit",
"test": "../../../node_modules/.bin/jest --config jest.config.cjs --runInBand"
},
"dependencies": {
"@actions/core": "1.11.1",
"@actions/github": "6.0.0"
},
"devDependencies": {
"@vercel/ncc": "0.38.4",
"typescript": "6.0.2"
}
}
This diff is collapsed.
import * as core from '@actions/core'
import { context, getOctokit } from '@actions/github'
import { runGate } from './gate'
async function main(): Promise<void> {
// Never accept a separately supplied token: the workflow's read-only job
// token is the only credential this action should see.
const token = process.env.GITHUB_TOKEN
if (!token) throw new Error('GITHUB_TOKEN is unavailable')
await runGate({ github: getOctokit(token), context, core })
}
main().catch((error: unknown) => {
// An unavailable token or unexpected entry-point error cannot make CI green:
// open the gate so the normal, required full-CI graph still runs.
core.warning(
`PR stack gate could not start; running full CI: ${String(error)}`
)
core.setOutput('skip', 'false')
})
{
"compilerOptions": {
"target": "es2024",
"module": "NodeNext",
"moduleResolution": "NodeNext",
"rootDir": "./src",
"strict": true,
"skipLibCheck": false,
"esModuleInterop": true
},
"include": ["src/**/*.ts"]
}
...@@ -75,6 +75,22 @@ importers: ...@@ -75,6 +75,22 @@ importers:
specifier: 0.38.4 specifier: 0.38.4
version: 0.38.4 version: 0.38.4
actions/pr-stack-ci-gate:
dependencies:
'@actions/core':
specifier: 1.11.1
version: 1.11.1
'@actions/github':
specifier: 6.0.0
version: 6.0.0
devDependencies:
'@vercel/ncc':
specifier: 0.38.4
version: 0.38.4
typescript:
specifier: 6.0.2
version: 6.0.2
actions/validate-docs-links: actions/validate-docs-links:
dependencies: dependencies:
'@actions/core': '@actions/core':
......
...@@ -22,11 +22,15 @@ env: ...@@ -22,11 +22,15 @@ env:
jobs: jobs:
optimize-ci: optimize-ci:
permissions:
checks: read
contents: read
pull-requests: read
uses: ./.github/workflows/pr_stack_optimizer.yml uses: ./.github/workflows/pr_stack_optimizer.yml
secrets: inherit
changes: changes:
name: Determine changes name: Determine changes
needs: ['optimize-ci']
runs-on: ubuntu-latest runs-on: ubuntu-latest
permissions: permissions:
contents: read contents: read
...@@ -157,6 +161,7 @@ jobs: ...@@ -157,6 +161,7 @@ jobs:
build-next: build-next:
name: build-next name: build-next
needs: ['optimize-ci']
permissions: permissions:
contents: read contents: read
id-token: write id-token: write
...@@ -251,11 +256,16 @@ jobs: ...@@ -251,11 +256,16 @@ jobs:
# `*.browser.{ts,tsx}` sibling was added/removed without running # `*.browser.{ts,tsx}` sibling was added/removed without running
# `pnpm generate-browser-variant-aliases` and committing the result. # `pnpm generate-browser-variant-aliases` and committing the result.
pnpm generate-browser-variant-aliases pnpm generate-browser-variant-aliases
pnpm --dir .github/actions/pr-stack-ci-gate install --frozen-lockfile --ignore-scripts
pnpm --dir .github/actions/pr-stack-ci-gate types
pnpm --dir .github/actions/pr-stack-ci-gate build
pnpm --dir .github/actions/pr-stack-ci-gate test
git diff --exit-code git diff --exit-code
stepName: 'lint' stepName: 'lint'
secrets: inherit secrets: inherit
validate-docs-links: validate-docs-links:
needs: ['optimize-ci']
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2 - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
......
# Avoid running the full CI on mid-stack PRs: https://graphite.dev/docs/stacking-and-ci # Avoid running the full CI concurrently on every PR in a branch-based stack.
# #
# This supports both Graphite stacks and GitHub's native stacked PRs. For either kind of stack, we # A stack is inferred from ordinary PR branch relationships (the next PR's base
# only run the full CI on the very top and very bottom of the stack. # branch is the previous PR's head branch). The first three PRs and every top
# # PR run immediately. A middle PR waits until any of its previous three PRs has
# We still run some high-signal low-cost jobs (e.g. lint, unit tests) on mid-stack PRs, just not # passed `thank you, next`, while a five-hour deadline fails open.
# anything slow (e.g. integration tests).
#
# Because we don't use Graphite's CI batching, full CI will still run on every PR individually
# before it merges. The goal is just to avoid wasting CI capacity when frequently rebasing large
# stacks.
#
# This can by bypassed by labeling a PR with 'CI Bypass PR Stack Optimization' (or the legacy
# 'CI Bypass Graphite Optimization' label), and manually re-running CI.
name: PR Stack Optimizer name: PR Stack CI Gate
on: on:
workflow_call: workflow_call:
outputs: outputs:
skip: skip:
description: "'true' if expensive CI checks should be skipped, 'false' otherwise." description: 'Kept for compatibility; expensive CI is never skipped after the gate opens.'
value: ${{ jobs.optimize-ci.outputs.skip }} value: ${{ jobs.optimize-ci.outputs.skip }}
secrets:
GRAPHITE_CI_OPTIMIZER_TOKEN: permissions: {}
description: 'The Graphite CI optimization secret'
# secrets are not available in forks, check-skip will just fail-open with a warning
required: false
env: env:
# FYI, if you add this label, you must *push* to the repository again to trigger a new event. Just BYPASS_LABEL: CI Bypass PR Stack Optimization
# re-running in the GitHub actions UI won't work, as it will re-use the old event with the old
# labels.
HAS_BYPASS_LABEL: |-
${{
github.event_name == 'pull_request' &&
(
contains(github.event.pull_request.labels.*.name, 'CI Bypass PR Stack Optimization') ||
contains(github.event.pull_request.labels.*.name, 'CI Bypass Graphite Optimization')
)
}}
# GitHub's native stacked PRs expose the PR's position within the stack. We skip expensive CI on
# mid-stack PRs. Fail open if we don't have `stack.size`.
IS_MID_STACK_NATIVE: |-
${{
github.event_name == 'pull_request' &&
github.event.pull_request.stack.size != '' &&
github.event.pull_request.stack.position != 1 &&
github.event.pull_request.stack.position != github.event.pull_request.stack.size
}}
jobs: jobs:
optimize-ci: optimize-ci:
name: PR Stack Optimizer name: PR Stack CI Gate
runs-on: ubuntu-latest runs-on: ubuntu-latest
timeout-minutes: 360
# The build-and-test caller grants these same read scopes; reusable
# workflows cannot increase the caller's GITHUB_TOKEN permissions.
permissions:
checks: read
contents: read
pull-requests: read
outputs: outputs:
# `== 'true'` comparison: If `step.check-skip` fails (`continue-on-error`), that output will skip: ${{ steps.gate.outputs.skip || steps.fork.outputs.skip }}
# be an empty string, which sets our `skip` output to `'false'`.
#
# We skip if either Graphite's optimizer says to skip, or the PR is a mid-stack PR in a
# GitHub native stack. The bypass label overrides both.
skip: ${{ env.HAS_BYPASS_LABEL == 'false' && steps.check-skip.outputs.skip == 'true' }}
# Note: IS_MID_STACK_NATIVE is disabled for now because it doesn't
# understand if we're not on the bottom of the stack, but all the PRs
# below us are merged.
# <https://vercel.slack.com/archives/C04KC8A53T7/p1783018076576349>
# || env.IS_MID_STACK_NATIVE == 'true'
steps: steps:
- name: Optimize CI # Do not check out or execute code supplied by a fork. It cannot be part
id: check-skip # of a same-repository branch stack, so let its full CI run immediately.
# Graphite's action is designed to fail open, but still sometimes fails if GH's infra flakes - name: Run full CI for fork PRs
continue-on-error: true id: fork
uses: withgraphite/graphite-ci-action@402a89bc8aa6db18ae1f9c61953d001d5f9d828f # main if: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name != github.repository }}
with:
graphite_token: ${{ secrets.GRAPHITE_CI_OPTIMIZER_TOKEN }}
- name: Debug Output
run: | run: |
echo 'github.event_name: ${{ github.event_name }}' set -euo pipefail
echo "secrets.GRAPHITE_CI_OPTIMIZER_TOKEN != '': ${GRAPHITE_CI_OPTIMIZER_TOKEN_NON_EMPTY}" echo 'skip=false' >> "$GITHUB_OUTPUT"
echo 'env.HAS_BYPASS_LABEL: ${{ env.HAS_BYPASS_LABEL }}' {
echo 'env.IS_MID_STACK_NATIVE: ${{ env.IS_MID_STACK_NATIVE }}' echo '# PR Stack CI Gate'
echo 'github.event.pull_request.stack.position: ${{ github.event.pull_request.stack.position }}' echo ''
echo 'github.event.pull_request.stack.size: ${{ github.event.pull_request.stack.size }}' echo '- Role: **fork**'
echo 'steps.check-skip.outputs.skip: ${{ steps.check-skip.outputs.skip }}' echo '- Result: **open**'
echo '- Reason: fork PRs always run immediately'
} >> "$GITHUB_STEP_SUMMARY"
# Fetch the compiled action from the exact commit this CI run tests.
- name: Check out stack gate from this CI commit
if: ${{ github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository }}
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
ref: ${{ github.sha }}
sparse-checkout: |
.github/actions/pr-stack-ci-gate/action.yml
.github/actions/pr-stack-ci-gate/dist/index.js
sparse-checkout-cone-mode: false
persist-credentials: false
- name: Wait for previous stack CI
id: gate
if: ${{ github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository }}
uses: ./.github/actions/pr-stack-ci-gate
env: env:
GRAPHITE_CI_OPTIMIZER_TOKEN_NON_EMPTY: ${{ secrets.GRAPHITE_CI_OPTIMIZER_TOKEN != '' }} GITHUB_TOKEN: ${{ github.token }}
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment