Question

An organization owner created an organization-level Actions secret named DEPLOY_TOKEN with its access policy set to 'Selected repositories', granting three repositories access. A new repository, 'payments-api', now needs to run a workflow that consumes DEPLOY_TOKEN, and the platform team wants to avoid duplicating the secret value in each repository. What is the most appropriate action to grant 'payments-api' access to the existing secret?

Accepted Answer

Edit the DEPLOY_TOKEN organization secret and add 'payments-api' to its list of selected repositories.

Answer

Create a new repository-level secret named DEPLOY_TOKEN in 'payments-api' with the same value.

Answer

Change the DEPLOY_TOKEN access policy to 'All repositories' so every repo including 'payments-api' can use it.

Answer

Fork one of the three authorized repositories into 'payments-api' so it inherits the secret access.