What does secrets: inherit accomplish when a caller workflow invokes a reusable workflow?
Select an answer to reveal the explanation.
Short Explanation and Infographic
secrets: inherit is the handoff so a trusted reusable workflow can use the caller's secrets without re-declaring every name — convenient, but only call reusable workflows you trust. It is not a license to dump secrets into logs or turn off scanning.
Full explanation below image
Full Explanation
The correct answer is that the reusable workflow receives secrets from the caller according to inherit semantics. This simplifies shared pipelines while keeping secret storage at the caller ownership boundary. Option A is incorrect and insecure. Option C is false. Option D is false. Review reusable workflow source, pin to SHAs for third-party workflows, and minimize secret exposure even with inherit.