Skip to content

ci: single required aggregator (CI Required) over the 10 required contexts#904

Draft
frstrtr wants to merge 1 commit into
masterfrom
ci-steward/ci-path-filter-aggregator
Draft

ci: single required aggregator (CI Required) over the 10 required contexts#904
frstrtr wants to merge 1 commit into
masterfrom
ci-steward/ci-path-filter-aggregator

Conversation

@frstrtr

@frstrtr frstrtr commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Reusable-workflow orchestrator so branch protection can require ONE context instead of 10, unblocking path-filter skips.

What

  • New ci-required.yml (workflow name: CI Required) fires on pull_request to master. It calls the 6 workflows carrying the 10 required contexts (coin-matrix + DASH G1/G3a + DGB Phase-B + BCH G3a/G3b) via workflow_call with secrets: inherit, then runs an aggregate job (needs: [all], if: always()).
  • aggregate fails on any lane that is failure/cancelled and tolerates skipped — so a PR that path-filters an untouched lane still merges.
  • workflow_call: added additively to the 6 workflows; their existing push/pull_request triggers and behaviour are unchanged.

Intended required context (post-merge, operator re-points branch protection)

CI Required / aggregate — replaces the 10 individual contexts.

Transition note

Until branch protection is re-pointed and the legacy direct triggers retired, the 6 lanes run both directly and under the aggregator on a PR. No concurrency collision: only coin-matrix has a concurrency group and it keys on github.workflow, which differs between the direct run and the reusable call.

Draft — held for operator branch-protection re-point after the single settle run.

…context workflows

Introduce a single reusable-workflow orchestrator (CI Required) that calls
coin-matrix + the 5 gate workflows and ends in an always()-run aggregate job.
The aggregate fails on any failed/cancelled lane and tolerates skipped, so
branch protection can require one context (CI Required / aggregate) in place
of the 10 individual contexts. This lets path-filtering skip untouched lanes
on a PR without blocking the merge.

workflow_call: is added additively to the 6 workflows; their existing push
and pull_request triggers and behaviour are unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant