Inherit secrets from publish workflow #70
Merged
Conversation
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
By default, workflows do not inherit secrets from other workflows that call them, even if they would otherwise have access via an event trigger. This setting re-enables access to secrets needed to run E2E tests when invoked from the publish workflow.
kyleknap
requested review from
anjaliratnam-msft,
jalauzon-msft,
seanmcc-msft and
vincenttran-msft
as code owners
anjaliratnam-msft
approved these changes
Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
By default, workflows do not inherit secrets from other workflows that call them, even if they would otherwise have access via an event trigger. This setting re-enables access to secrets needed to run E2E tests as part of the CI workflow when invoked from the publish workflow. See documentation for more details.