jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 03:16:52 -05:00
Code Issues Projects Releases Wiki Activity

Codespaces: change 'encrypted secrets' to 'secrets' (#41416)

Browse Source
This commit is contained in:
hubwriter
2023-09-04 11:25:21 +01:00
committed by GitHub
parent bec13b6e58
commit 57d47a08af
57 changed files with 111 additions and 105 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/codespaces/codespaces-reference/security-in-github-codespaces.md
View File

@@ -78,15 +78,15 @@ Codespaces are designed to be security hardened by default. To help maintain thi
### Using secrets to access sensitive information
Always use encrypted secrets when you want to use sensitive information (such as access tokens) in a codespace. You can access your secrets as environment variables in the codespace, including from the terminal. For example, you can launch a terminal within your codespace and use `echo $SECRET_NAME` to see the value of a secret.
Always use secrets when you want to use sensitive information (such as access tokens) in a codespace. You can access your secrets as environment variables in the codespace, including from the terminal. For example, you can launch a terminal within your codespace and use `echo $SECRET_NAME` to see the value of a secret.
The secret values are copied to environment variables whenever the codespace is resumed or created and are also synced when they are changed.
Secrets are not copied into the environment if you don't have write access to the codespace's repository.
For more information on secrets, see:
- "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"
- "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)"
- "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-secrets-for-your-codespaces)"
- "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/managing-secrets-for-your-repository-and-organization-for-github-codespaces)"
### Working with other people's contributions and repositories
@@ -94,7 +94,7 @@ When you create a codespace from a PR branch from a fork, the token in the codes
- For a private repository, the codespace is granted access to both the fork and parent.
- For a public repository, the codespace will only have access to the fork and opening PRs on the parent.
We also further protect you in these scenarios by not injecting any of your [codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) into the environment.
We also further protect you in these scenarios by not injecting any of your [codespace secrets](/codespaces/managing-your-codespaces/managing-secrets-for-your-codespaces) into the environment.
{% note %}