When calling a reusable workflow, what does 'secrets: inherit' do?
Select an answer to reveal the explanation.
Short Explanation and Infographic
secrets: inherit is the master key — it passes all the caller's accessible secrets to the reusable workflow without listing them one by one.
Full explanation below image
Full Explanation
'secrets: inherit' in the calling workflow passes all secrets accessible to the caller (repository, organization, and environment secrets) to the called reusable workflow. Without this, the called workflow can only access secrets explicitly listed in the 'secrets:' block. This is useful when the reusable workflow needs many secrets or when the exact secret names aren't known at authoring time. Secrets are passed securely — they don't appear in logs. 'inherit' only passes secrets from the calling context, not from other repositories or organizations not already accessible. Secrets are not copied or stored, just forwarded for the duration of the run.