What does secrets: inherit accomplish when a caller workflow invokes a reusable workflow?
Select an answer to reveal the explanation.
Short Explanation
secrets: inherit hands the reusable workflow access to the caller's secrets without re-declaring every name. Use it only with workflows you trust. It doesn't dump secrets into logs or turn off scanning.
Full Explanation
The correct answer is that the reusable workflow receives secrets from the caller workflow's scope as designed by the inherit setting. This simplifies shared pipelines while keeping secret storage at the caller ownership boundary. The option saying it permanently prints all secrets to the job summary is incorrect and insecure. The option saying it disables secret scanning for the repository is false. The option saying it converts secrets into public repository variables is false. Review reusable workflow source, pin to SHAs for third-party workflows, and minimize secret exposure even with inherit.