[repo]: Add opt-in auto-merge for plugin update PRs#185
Merged
Conversation
|
This PR is currently a draft. Plugin validation will run once the PR is marked ready for review. |
sethwv
marked this pull request as ready for review
July 18, 2026 18:15
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.
Summary
.github/workflows/auto-merge-updates.yml, gated behind a newAUTO_MERGE_UPDATESrepo variable (off by default).Validate Pluginsucceeds — but only for pure plugin version-bump updates.How it works
workflow_runcompletion ofValidate Plugin; no-ops unlessAUTO_MERGE_UPDATES == 'true'.GH_APP_ID/GH_APP_PRIVATE_KEY) isn't configured — merging with the plainGITHUB_TOKENwouldn't cascade intopublish-plugins.yml's push trigger, so we never fall back to it for this.head_shaagainst open PRs (more reliable thanworkflow_run.pull_requestsfor fork-originatedpull_request_targetruns).Plugin Updatelabel; rejectsNew Plugin,Repo Update,Invalid, orQUARANTINElabels, and requires a cleanMERGEABLEstate.plugins/, every touched plugin slug already exists onmain) as defense-in-depth against label tampering, rather than trusting labels alone.publish-plugins.yml.