Skip to content

docs: Dependabot auto-merge calls the shared workflow - #19

Merged
thatsrue merged 1 commit into
mainfrom
docs/automerge-shared-workflow
Nov 10, 2026
Merged

thatsrue merged 1 commit into
mainfrom
docs/automerge-shared-workflow

Conversation

@thatsrue

Copy link
Copy Markdown
Collaborator

What changed

docs/repo-standards.md, Dependabot: auto-merge is an automerge job that calls the shared dependabot-auto-merge.yml here, pinned to a commit SHA, instead of each repo carrying its own copy of the steps. The pattern it follows is unchanged: dependabot/fetch-metadata, no majors, gh pr merge --squash --match-head-commit, and needs: on every other job.

Why

Two shapes are live: 13 repos carry an inline automerge job, and openclaw-context-pacer calls the shared workflow, which merged its Dependabot group PR (#88) on its own on 2026-11-09. The text described only the inline copy. One tested copy beats 13 that can drift: the pre-push hook needed about 55 fix PRs across copies before it moved to one template. The owner chose the shared workflow on 2026-11-09. The inline repos move over one PR each.

No issue: docs

How you checked it

  • scripts/check: 0, also through the pre-push hook.

  • The link to .github/workflows/dependabot-auto-merge.yml resolves from docs/.

  • 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 87d4c66 into main Nov 10, 2026
1 check passed
@thatsrue
thatsrue deleted the docs/automerge-shared-workflow branch November 10, 2026 04:07
thatsrue added a commit that referenced this pull request Nov 10, 2026
…g repos can deploy (#20)

## What changed

- `.github/workflows/dependabot-auto-merge.yml`: a `merged` output, `'true'` when the run merged the pull request. The header shows a `deploy-merged` job that starts a repo's deploy workflow when it is.
- `docs/repo-standards.md`, Dependabot: a repo that deploys on push to `main` adds that job.

## Why

Five site repos (codeserious-site, occasional-wotd, wordbug, wordbun, shadecaster) carry an inline auto-merge job with an extra step: after merging, it runs `deploy.yml`, because a merge made with `GITHUB_TOKEN` starts no workflows. The shared workflow had no way to say it merged, so moving those repos to it (#19) would drop their deploys. Repos that don't deploy ignore the output.

No issue: ci

## How you checked it

- `actionlint` on the workflow: 0. `scripts/check`: 0, also through the pre-push hook.
- Not run end to end: act can't fake a Dependabot pull request, and the merge step only runs for one. The output reads the merge step's `outcome`, the same way the inline jobs do. The first Dependabot minor or patch PR on a site repo after it moves over is the live check.

- [ ] A bug fix comes with a test that fails without it
- [x] Docs match how it works now
- [x] No secrets or private information
thatsrue added a commit to splitleafhq/aethergram that referenced this pull request Nov 10, 2026
## What changed

The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`.

## Why

The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

No issue: chore.

Change class: CI config, no behavior change.

## How you checked it

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.

- [ ] A bug fix comes with a test that fails without it
- [x] Docs match how it works now
- [x] No secrets or private information
thatsrue added a commit to splitleafhq/cairn that referenced this pull request Nov 10, 2026
## What changed

The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`.

## Why

The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

No issue: chore.

Change class: CI config, no behavior change.

## How you checked it

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.

- [ ] A bug fix comes with a test that fails without it
- [x] Docs match how it works now
- [x] No secrets or private information
thatsrue added a commit to seriouslysean/dndb-product-ownership that referenced this pull request Nov 10, 2026
## What changed

The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`.

## Why

The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

No issue: chore.

Change class: CI config, no behavior change.

## How you checked it

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.

- [ ] A bug fix comes with a test that fails without it
- [x] Docs match how it works now
- [x] No secrets or private information
thatsrue added a commit to seriouslysean/discord-server-events-feed that referenced this pull request Nov 10, 2026
## What changed

The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`.

## Why

The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

No issue: chore.

Change class: CI config, no behavior change.

## How you checked it

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.

- [ ] A bug fix comes with a test that fails without it
- [x] Docs match how it works now
- [x] No secrets or private information
thatsrue added a commit to seriouslysean/codeserious-site that referenced this pull request Nov 10, 2026
## What changed

The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`. The post-merge deploy moves to a deploy-merged job in this file, which runs `gh workflow run deploy.yml --ref main` when the shared workflow's `merged` output is true, as before.

## Why

The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

No issue: chore.

Change class: CI config, no behavior change. The post-merge deploy moves to a deploy-merged job.

## How you checked it

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge` or `deploy-merged`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.

- [ ] A bug fix comes with a test that fails without it
- [x] Docs match how it works now
- [x] No secrets or private information
thatsrue added a commit to seriouslysean/shadecaster that referenced this pull request Nov 14, 2026
## What changed

The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`. The post-merge deploy moves to a deploy-merged job in this file, which runs `gh workflow run deploy.yml --ref main` when the shared workflow's `merged` output is true, as before.

## Why

The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

No issue: chore.

Change class: CI config, no behavior change. The post-merge deploy moves to a deploy-merged job.

## How you checked it

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge` or `deploy-merged`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.

- [ ] A bug fix comes with a test that fails without it
- [x] Docs match how it works now
- [x] No secrets or private information
thatsrue added a commit to seriouslysean/occasional-wotd that referenced this pull request Nov 14, 2026
## Summary

- The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`. The post-merge deploy moves to a deploy-merged job in this file, which runs `gh workflow run deploy.yml --ref main` when the shared workflow's `merged` output is true, as before.
- Why: The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

Change class: CI config, no behavior change. The post-merge deploy moves to a deploy-merged job.

## Test plan

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge` or `deploy-merged`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.
- [x] Quality gates pass (lint, typecheck, test, build) via `scripts/check`
- [ ] Relevant tests added or updated: none, CI config only
- [ ] Manual verification if applicable: see above
thatsrue added a commit to seriouslysean/wordbug that referenced this pull request Nov 14, 2026
## Summary

- The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`. The post-merge deploy moves to a deploy-merged job in this file, which runs `gh workflow run deploy.yml --ref main` when the shared workflow's `merged` output is true, as before.
- Why: The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

Change class: CI config, no behavior change. The post-merge deploy moves to a deploy-merged job.

## Test plan

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge` or `deploy-merged`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.
- [x] Quality gates pass (lint, typecheck, test, build) via `scripts/check`
- [ ] Relevant tests added or updated: none, CI config only
- [ ] Manual verification if applicable: see above
thatsrue added a commit to seriouslysean/wordbun that referenced this pull request Nov 14, 2026
## Summary

- The inline `automerge` job in `.github/workflows/ci.yml` now calls `splitleafhq/.github/.github/workflows/dependabot-auto-merge.yml`, pinned to df79f9c. It keeps the same `needs:` list and `if:`, and its `contents` and `pull-requests` write permissions; the job's `name:` is dropped, so the check name is `automerge`, the same as its id. No ruleset or required check names the old `Dependabot auto-merge`. The post-merge deploy moves to a deploy-merged job in this file, which runs `gh workflow run deploy.yml --ref main` when the shared workflow's `merged` output is true, as before.
- Why: The owner chose the shared workflow on 2026-11-09: one tested copy of the steps instead of a copy in each repo (splitleafhq/.github#19 and #20).

Change class: CI config, no behavior change. The post-merge deploy moves to a deploy-merged job.

## Test plan

- `actionlint .github/workflows/ci.yml`: 0.
- `scripts/check`: 0.
- act: not run for `automerge` or `deploy-merged`. They only run for a Dependabot PR, which act can't fake. Checked instead by actionlint, and by the call matching the shape in splitleafhq/.github `.github/workflows/dependabot-auto-merge.yml` and openclaw-context-pacer's `ci.yml`; the first real Dependabot PR after merge is the live check.
- [x] Quality gates pass (lint, typecheck, test, build) via `scripts/check`
- [ ] Relevant tests added or updated: none, CI config only
- [ ] Manual verification if applicable: see above
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