jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-06 15:01:04 -05:00
Code Issues Projects Releases Wiki Activity

chore: remove typo

Browse Source
This commit is contained in:
kamilkulik
2023-02-08 07:32:44 +01:00
committed by GitHub
parent 952bf405c1
commit 67c97e28c9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
View File

@@ -46,7 +46,7 @@ Your organization can share workflows by reusing the workflows exactly or by cre
## Sharing secrets{% ifversion actions-configuration-variables %} and variables{% endif %} within an organization
You can centrally manage your secrets {% ifversion actions-configuration-variables %} and variables{% endif %} within an organization, and then make them available to selected repositories. This also means that you can update a secret {% ifversion actions-configuration-variables %} or variable{% endif %} in one location, and have the change apply to all repository workflows that use the it.
You can centrally manage your secrets {% ifversion actions-configuration-variables %} and variables{% endif %} within an organization, and then make them available to selected repositories. This also means that you can update a secret {% ifversion actions-configuration-variables %} or variable{% endif %} in one location, and have the change apply to all repository workflows that use it.
When creating a secret {% ifversion actions-configuration-variables %} or variable{% endif %} in an organization, you can use a policy to limit which repositories can access it. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.