How do GitHub organization-level secrets differ from repository-level secrets in GitHub Actions?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Org secrets are the DRY principle applied to credentials. Instead of adding your AWS access key to 50 different repositories, you put it once in the org and share it with the repos that need it. One update, all repos get the new value.
Full explanation below image
Full Explanation
GitHub Actions secrets can be scoped at three levels: repository, environment, and organization. Organization-level secrets provide: (1) Centralized management — define a secret once and share it across selected repositories. (2) Access control — org owners choose which repositories can access each org secret (all repos, selected repos, or only private repos). (3) Simplified rotation — update the secret in one place and all using repos automatically get the new value. (4) Reduced duplication — no need to set the same credential in dozens of repositories. Repository-level secrets take precedence over org-level secrets of the same name (secret resolution order: environment → repository → organization). Both levels use the same encryption mechanism (libsodium). There's no difference in encryption strength between levels.