Repository navigation
ci(automerge): report whether the shared workflow merged, so deploying repos can deploy - #20
Merged
Merged
Conversation
…g repos can deploy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
.github/workflows/dependabot-auto-merge.yml: amergedoutput,'true'when the run merged the pull request. The header shows adeploy-mergedjob that starts a repo's deploy workflow when it is.docs/repo-standards.md, Dependabot: a repo that deploys on push tomainadds 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 withGITHUB_TOKENstarts 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
actionlinton 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