ci: run rust CI on active development branches - #623
Open
blacks1ne wants to merge 1 commit into
Open
Conversation
blacks1ne
force-pushed
the
fix/ci-active-branch-trigger
branch
2 times, most recently
from
August 27, 2026 14:14
fa93c23 to
74e5100
Compare
blacks1ne
force-pushed
the
fix/ci-active-branch-trigger
branch
2 times, most recently
from
September 6, 2026 15:00
493609d to
969c214
Compare
blacks1ne
force-pushed
the
fix/ci-active-branch-trigger
branch
from
September 8, 2026 07:11
969c214 to
b600970
Compare
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
1 participant
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.
Base:
f5b671a6rust-ci.ymlruns three jobs:build(cargo check),test(cargo nextest),and a
release-buildmatrix over linux-x86_64, linux-arm64 and macos-arm64.It has two triggers.
pull_request:carries no branch filter, so every PR iscovered whatever its base — unchanged here.
push:wasbranches: [develop]and nothing else.
Development doesn't land on
develop. It lands on the versioned branch(
v2.1.0.25today) and on milestone branches (develop-2.1), which are alsowhat PRs target. A push to those ran no CI at all, so anything broken there was
first seen by whoever opened the next PR, reported against their branch.
The push trigger becomes
[develop, 'develop-*', 'v[0-9]*'].Cost is one run per push to those branches.
concurrency: rust-ci-${{ github.ref }}with
cancel-in-progress: trueis already set, so a burst of pushes to onebranch keeps one run rather than queueing.
The red checks here are the LFS budget, not this diff — and they make the point:
a repository-wide fault currently surfaces only on contributors' PRs, never on
the branch that carries it.
Validation:
git diff --check; the workflow YAML parses.