Pass the wall its deploy key by name - #15
Merged
Merged
Conversation
secrets: inherit only reaches a reusable workflow in the same organisation, and the wall lives under YauhenBichel, so it passed nothing. The wall fell back to the workflow token, which the protected main refuses: every run logged WITH_DEPLOY_KEY false, and the org profile's wall failed with GH013 on its first real push. The key is now passed explicitly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Thanks for passing the wall its deploy key by name, @YauhenBichel!
|
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.
Sorry — a follow-up to the wall change from earlier today.
secrets: inheritonly works for a reusable workflow in the same organisation. The wall lives under YauhenBichel, so the deploy key never arrived: every run loggedWITH_DEPLOY_KEY: falseand would fall back to the token, which protectedmainrefuses. It went unnoticed here only because nothing needed pushing yet.This passes
CONTRIBUTORS_DEPLOY_KEYto the wall explicitly. Nothing else changes.🤖 Generated with Claude Code