Skip to content

ci: merge Dependabot patch and minor updates with the shared workflow - #101

Merged
thatsrue merged 2 commits into
mainfrom
ci/dependabot-automerge
Nov 20, 2026
Merged

thatsrue merged 2 commits into
mainfrom
ci/dependabot-automerge

Conversation

@thatsrue

@thatsrue thatsrue commented Nov 20, 2026 •

Copy link
Copy Markdown
Collaborator

What changed

  • .github/workflows/ci.yml: an automerge job after every other job, for pull requests opened by dependabot[bot] only. It calls the shared workflow in splitleafhq/.github (dependabot-auto-merge.yml), pinned to a commit: a patch or minor update squash-merges once those jobs pass, pinned to the head they tested; a major stays open for a person.

Why

Dependabot pull requests here wait for a person to merge them. The shared repository standards have this job for that ("Dependabot auto-merge" in splitleafhq/.github docs/repo-standards.md), and sibling repositories that already carry it merge their updates on green. The job asks for contents: write and pull-requests: write for itself only. This changes CI behaviour: CI will merge some pull requests by itself.

CI here runs the VAD tests and a tiny-model whisper test, so an update that breaks install, VAD or whisper load and decode fails before this job can merge it. mlx and mlx-whisper updates merge with the rest though CI cannot exercise them; the repository's rules say so and what to run before relying on that path.

No issue: ci.

How you checked it

  • scripts/check: 0.

  • actionlint .github/workflows/ci.yml: 0.

  • The job is the one sibling repositories carry; the pin is the commit other repositories already pin.

  • Not shown until Dependabot's next pull request here: a real merge through it, and a major left open.

  • A bug fix comes with a test that fails without it

  • Docs match how it works now

  • No secrets or private information

@thatsrue
thatsrue merged commit 2c89427 into main Nov 20, 2026
5 checks passed
@thatsrue
thatsrue deleted the ci/dependabot-automerge branch November 20, 2026 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant