feat(ci): skip non-frontend stacks on frontend-only PRs#4626
Merged
Yicong-Huang merged 4 commits intoMay 2, 2026
Merged
Conversation
Yicong-Huang
added
the
release/v1.1.0-incubating
Mirror of the existing "skip frontend if no `frontend` label" rule.
When the PR's labels are a subset of {frontend, docs, dev} and the
`frontend` label is present, skip scala / python / agent-service so
a pure frontend change does not pay the ~30 minutes for stacks it
cannot affect.
Decision table:
| labels | frontend | scala | python | agent-service |
| ------------------------------------------ | -------- | ----- | ------ | ------------- |
| only docs / dev | skip | skip | skip | skip |
| frontend (with optional docs/dev) | run | skip | skip | skip |
| no frontend label | skip | run | run | run |
| any other combination | run | run | run | run |
Closes apache#4625
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Yicong-Huang
force-pushed
the
feat/skip-non-frontend-on-frontend-only-pr
branch
from
50a23f6 to
5c1e571
Compare
2 tasks
github-actions Bot
pushed a commit
that referenced
this pull request
May 2, 2026
### What changes were proposed in this PR?
Skip the non-frontend stacks (`scala`, `python`, `agent-service`) when a
PR's labels are a subset of `{frontend, docs, dev}` and `frontend` is
present. Mirror of the existing "skip frontend if no `frontend` label"
rule from #4622.
Updated `precheck` decision table:
| PR labels | frontend | scala | python | agent-service |
|---|---|---|---|---|
| only `docs` and/or `dev` | skip | skip | skip | skip |
| `frontend` (with optional `docs` / `dev`) | **run** | **skip** |
**skip** | **skip** |
| no `frontend` label | skip | run | run | run |
| any other combination | run | run | run | run |
The backport matrix automatically inherits the same skip decisions
through the existing `run_*` plumbing in `required-checks.yml`.
### Any related issues, documentation, discussions?
Closes #4625. Builds on #4622 (this PR is stacked on
`feat/label-based-stack-routing`).
### How was this PR tested?
To exercise after merge: open a frontend-only PR (only `frontend/**`
files, labels: just `frontend`); precheck should set `run_frontend=true`
and the other three to `false`. Open a docs-only PR for the all-skip
path; open a python-only PR for the existing "skip frontend" path.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
(backported from commit 1e996cd)
SarahAsad23
pushed a commit
to SarahAsad23/texera
that referenced
this pull request
May 4, 2026
### What changes were proposed in this PR?
Skip the non-frontend stacks (`scala`, `python`, `agent-service`) when a
PR's labels are a subset of `{frontend, docs, dev}` and `frontend` is
present. Mirror of the existing "skip frontend if no `frontend` label"
rule from apache#4622.
Updated `precheck` decision table:
| PR labels | frontend | scala | python | agent-service |
|---|---|---|---|---|
| only `docs` and/or `dev` | skip | skip | skip | skip |
| `frontend` (with optional `docs` / `dev`) | **run** | **skip** |
**skip** | **skip** |
| no `frontend` label | skip | run | run | run |
| any other combination | run | run | run | run |
The backport matrix automatically inherits the same skip decisions
through the existing `run_*` plumbing in `required-checks.yml`.
### Any related issues, documentation, discussions?
Closes apache#4625. Builds on apache#4622 (this PR is stacked on
`feat/label-based-stack-routing`).
### How was this PR tested?
To exercise after merge: open a frontend-only PR (only `frontend/**`
files, labels: just `frontend`); precheck should set `run_frontend=true`
and the other three to `false`. Open a docs-only PR for the all-skip
path; open a python-only PR for the existing "skip frontend" path.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
Skip the non-frontend stacks (
scala,python,agent-service) when a PR's labels are a subset of{frontend, docs, dev}andfrontendis present. Mirror of the existing "skip frontend if nofrontendlabel" rule from #4622.Updated
precheckdecision table:docsand/ordevfrontend(with optionaldocs/dev)frontendlabelThe backport matrix automatically inherits the same skip decisions through the existing
run_*plumbing inrequired-checks.yml.Any related issues, documentation, discussions?
Closes #4625. Builds on #4622 (this PR is stacked on
feat/label-based-stack-routing).How was this PR tested?
To exercise after merge: open a frontend-only PR (only
frontend/**files, labels: justfrontend); precheck should setrun_frontend=trueand the other three tofalse. Open a docs-only PR for the all-skip path; open a python-only PR for the existing "skip frontend" path.Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 4.7