Skip to content

chore(ci): trigger on all branch pushes#23

Merged
rocketman-code merged 1 commit intomainfrom
ci-trigger-push
Apr 14, 2026
Merged

chore(ci): trigger on all branch pushes#23
rocketman-code merged 1 commit intomainfrom
ci-trigger-push

Conversation

@rocketman-code
Copy link
Copy Markdown
Owner

@rocketman-code rocketman-code commented Apr 14, 2026

Summary

  • CI trigger changed from pull_request: branches: [main] to push: branches: ['**'].
  • Runs CI on every branch push (covers stacked PRs and pre-PR feature branches that were previously unverified). Skips tag pushes, which are handled by COPR.
  • Switches $GITHUB_HEAD_REF to $GITHUB_REF_NAME in the clone command because the former is only set for pull_request events.

Why

PR #22 (rollback-scope, stacked on #21) had no CI runs because its base was not main. Untested code should not reach main; under the trust contract atomic-rollback operates by, that is a hard floor.

Test plan

  • CI runs on push to this branch (verifies the new trigger fires)
  • Both x86_64 and aarch64-cross checks pass

CI previously ran only on PRs to main (`pull_request: branches: [main]`).
Stacked PRs targeting other feature branches and pre-PR branch pushes
were not verified. Switching to `push: branches: ['**']` runs CI on
every branch push, skipping tags (which are handled by COPR).

The x86_64 job switches from `$GITHUB_HEAD_REF` to `$GITHUB_REF_NAME`
because the former is set only for pull_request events.
@rocketman-code rocketman-code merged commit 9dd57af into main Apr 14, 2026
2 checks passed
@rocketman-code rocketman-code deleted the ci-trigger-push branch April 14, 2026 06:26
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