Repository navigation
fix: use configured app secrets in consumer workflows - #129
Merged
Merged
Conversation
Signed-off-by: Vitor Mattos <vitor@php.rio>
Signed-off-by: Vitor Mattos <vitor@php.rio>
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.
Aligns consumer workflows with the existing LibreCode Workflow Automation credential contract.
Prepare releasenow reads both GitHub App credentials from Actions secrets;github-workflows v0.6.2, which validates credentials before planning and fixes authorization summary quoting;Update workflowsuses the same secret-backed App id instead of looking for a repository variable;vars.LIBRECODE_WORKFLOW_APP_IDform.This fixes the empty App id observed in LibreSign run 35667899070 without requiring a new secret value if the existing secret is already configured in the consumer context.