Use shared render action as PR merge gate#13
Draft
shielded-nate with Copilot wants to merge 1 commit into
Draft
Conversation
Copilot
AI
changed the title
Use shared render action for PR merge checks
Use shared Jun 17, 2026
render action as PR merge gate
Copilot created this pull request from a session on behalf of
shielded-nate
June 17, 2026 01:41
View session
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.
This updates PR render checks so merge acceptance is driven by the shared
renderaction path, aligned with repository rendering behavior. The PR workflow now invokes the composite render action directly instead of maintaining a separate inline render pipeline.Workflow gate alignment
.github/workflows/render.ymlnow uses./.github/actions/renderfor the PRrenderjob.rendercheck the canonical merge criterion via the reusable action.Refactor of PR render workflow
base_refsetup in the workflow so protocol conditional build logic remains available to the composite action.Resulting execution path