Skip to content

ci(automerge): report whether the shared workflow merged, so deploying repos can deploy - #20

Merged
thatsrue merged 1 commit into
mainfrom
ci/automerge-merged-output
Nov 10, 2026
Merged

thatsrue merged 1 commit into
mainfrom
ci/automerge-merged-output

Conversation

@thatsrue

Copy link
Copy Markdown
Collaborator

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

  • Docs match how it works now

  • No secrets or private information

@thatsrue
thatsrue merged commit eea5da8 into main Nov 10, 2026
1 check passed
@thatsrue
thatsrue deleted the ci/automerge-merged-output branch November 10, 2026 04:21
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