Your organization has a secret that must be available to all the repositories within GitHub Actions workflows.
You need to store the secret. The solution must minimize administrative effort.
What should you do in GitHub?
The correct solution is to create an organization-level Actions secret. This minimizes administrative effort because the secret can be managed once at the organization level and made available to all repositories or selected repositories through an access policy. Option D gives the correct navigation path: organization page, Settings, Secrets and variables, then Actions. Option A would require duplicating the secret in every repository, increasing maintenance overhead and risk of inconsistent values. Option B is wrong because personal developer settings do not centrally expose a secret to all organization repositories. Option C is incomplete because the current GitHub path places Actions secrets under ''Secrets and variables,'' not just a generic ''Security > Secrets'' location. GitHub documents organization secrets and the repository access policy model for sharing them.
Currently there are no comments in this discussion, be the first to comment!