feedBack/.github/workflows/ship-ci.yml
OmikronApex 005270608b
ci: adapt workflows to trunk-based development (#728)
Nightly builds main directly (old release/v* discovery pinned nightlies
to shipped branches forever). ship-ci adds push triggers on main and
release/** for post-merge signal. New rc.yml builds :rc images from
release branches during stabilization.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-03 11:25:44 +02:00

25 lines
759 B
YAML

name: ship-ci
# PRs into both main and release/** run CI through this wrapper so the check
# runs are named "ci / <job>" (reusable-workflow caller prefix), matching the
# org rulesets' required contexts. ci.yml itself only triggers via
# workflow_call — it never runs standalone, which would emit unprefixed
# "<job>" checks that the rulesets can't match.
on:
pull_request:
branches: [main, 'release/**']
# Trunk-based: post-merge CI on main catches semantic conflicts between
# independently-green PRs; push on release/** covers stabilization
# cherry-picks that land without a PR.
push:
branches: [main, 'release/**']
permissions:
contents: read
pull-requests: read
checks: read
jobs:
ci:
uses: ./.github/workflows/ci.yml