Repository navigation
Merge the automated Connect release update when Site checks pass - #93
Merged
Merged
Conversation
Callum decided Downloads updates should merge automatically. A workflow_run job merges only the release App's update pull request, at the exact checked head, and only when it changes the two release files. No repository merge settings change.
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.
Callum decided Downloads updates should merge automatically. This covers only the automated
website-updatepull request.merge-connect-release.ymlruns whenSite checkscompletes and merges with--match-head-commitwhen all of these hold:automation/connect-release-v*branch;main;site-sources.jsonandsrc/data/connect-release.json.A branch matching the name but failing those conditions fails the job and isn't merged. A behind branch is updated, because
mainrequires up-to-date checks, and the fresh check run on its new head merges it. The merge uses the App token, so it triggers the normal deploy onmain.This doesn't use GitHub auto-merge, because that needs a repository setting available to every pull request. Branch protection and all other pull requests are unchanged.
To be proven on the next Desktop release; the daily limit opens at 18:42Z on 2026-11-05. The guard was checked against #92's real fields and passes.