Skip to content

ci: trigger the Rust workflow on master - #172

Merged
pathscale merged 1 commit into
masterfrom
fix/ci-trigger-on-master
Jul 27, 2026
Merged

ci: trigger the Rust workflow on master#172
pathscale merged 1 commit into
masterfrom
fix/ci-trigger-on-master

Conversation

@pathscale

Copy link
Copy Markdown
Owner

The workflow's push/pull_request triggers only listed main, but the repository's only branch (and GitHub default) is master. Result: pushes to master and PRs targeting it run no checks at all#171 was merged with "no checks reported", and the merge commit c94e9a7 on master started no run either. The historical runs all carry head_branch: main, so CI went dark whenever that branch stopped being pushed.

This adds master to both triggers (keeping main in case of a future rename). Once merged, the next push to master will produce the first CI verdict on the flush fix.

Relevant to the 0.9.0 release: the working agreement gates cargo publish on a green merged default branch, which is impossible while CI never runs on it.

🤖 Generated with Claude Code

The workflow only listened to "main", but the repository's only branch
(and GitHub default) is "master": pushes to master and PRs targeting it
-- including the merged flush fix in #171 -- run no checks at all, so
the suite silently stopped gating anything. Keep "main" in the list in
case the branch is ever renamed.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@pathscale
pathscale merged commit eadc5ad into master Jul 27, 2026
2 of 3 checks passed
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