require-signed-release: write the way forward on an unsigned verdict - #57
Merged
Conversation
An unsigned verdict rehearses instead of failing, but the notice names no concrete next step. The opt-in unsigned-guidance input puts the exact companion commands into the step summary: fetch the tag, sign the companion on the release commit, push it. The companion's name derives from the attestation-tags glob, so v*-sig suggests vX.Y.Z-sig and the default glob suggests <tag>-sig. Pipelines that print their own guidance keep the plain notice.
gronke
force-pushed
the
unsigned-guidance
branch
from
August 24, 2026 13:17
c72b644 to
8a3831c
Compare
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
1 participant
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.
An unsigned verdict rehearses instead of failing, but the notice names no concrete next step. The opt-in unsigned-guidance input puts the exact companion commands into the step summary: fetch the tag, sign the companion on the release commit, push it. The companion's name derives from the attestation-tags glob, so
v*-sigsuggestsvX.Y.Z-sigand the default glob suggests<tag>-sig. Pipelines that print their own guidance keep the plain notice.