Skip to content

CI trigger, weekly run, and badge link - #59

Closed
nertzy wants to merge 3 commits into
masterfrom
ci-housekeeping
Closed

nertzy wants to merge 3 commits into
masterfrom
ci-housekeeping

Conversation

@nertzy

@nertzy nertzy commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator

Three small CI housekeeping changes, one commit each.

Only run CI on pushes to master. The push trigger also listed a
github-actions branch that no longer exists, so the only thing it could
still do was run the suite twice for a branch by that name — once for the
push and once for its pull request.

Run CI every week (schedule, Saturdays 18:00 UTC, plus
workflow_dispatch). The matrix includes Active Record's main and
*-stable branches, which move without anything happening here, so a break
in an unreleased Active Record currently waits for the next push to this
repository to surface. A weekly run catches it while the upstream change is
still fresh.

Link the build badge to master's runs. The badge image was already
pinned with ?branch=master, but its link went to the workflow's
unfiltered run list, where a pull request's run is usually the first thing
shown — so a green badge could lead to a red run for an unmerged branch.
The link now carries ?query=branch%3Amaster to match the image.

Two pre-existing nits in ci.yml are left alone here, happy to take either
in a follow-up: actions/checkout@v3 is old enough that GitHub warns about
its Node runtime, and the steps: entries are indented two spaces short of
what yamllint wants.

nertzy added 3 commits July 27, 2026 17:27
The github-actions branch no longer exists, so the one thing this entry can
still do is run the suite twice for any branch that happens to be named
github-actions -- once for the push and once for its pull request.

Pull requests are already covered by the pull_request trigger, so limiting
push to the trunk leaves every branch tested exactly once before it lands.
The matrix includes Active Record's main and *-stable branches, which move
without anything happening in this repository, so a break in an unreleased
Active Record only surfaces on the next push here -- possibly months later.
A weekly run surfaces it while the change is still fresh upstream.

workflow_dispatch comes along so the same suite can be started by hand
without an empty commit.
The badge image is already pinned to master, but clicking it landed on the
workflow's unfiltered run list, where a pull request's run is usually the
first thing shown -- so a green badge could lead to a red run for a branch
that had not merged.
@nertzy nertzy closed this Jul 27, 2026
@nertzy
nertzy deleted the ci-housekeeping branch July 27, 2026 22:31
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