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

Fix trailing spaces in content and data (#37904)

Browse Source
This commit is contained in:
Grace Park
2023-06-23 10:45:10 -07:00
committed by GitHub
parent 07dcb8c294
commit cbda3f2434
369 changed files with 642 additions and 641 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/codespaces/setting-up-your-project-for-codespaces/configuring-dev-containers/specifying-recommended-secrets-for-a-repository.md
View File

@@ -38,7 +38,7 @@ Each recommended secret is displayed in one of three ways:
### When to specify recommended secrets for a project
You should use recommended secrets for secrets that the user who creates the codespace, rather than the owner of the repository or organization, must provide. For example, if you have a public project, and users must provide a personal API key to run the application in your project, you can specify a recommended secret so that users will be prompted to provide the key as the value of the secret when they use the advanced options page to create a codespace.
You should use recommended secrets for secrets that the user who creates the codespace, rather than the owner of the repository or organization, must provide. For example, if you have a public project, and users must provide a personal API key to run the application in your project, you can specify a recommended secret so that users will be prompted to provide the key as the value of the secret when they use the advanced options page to create a codespace.
Alternatively, for secrets that the owner of the repository or organization can provide, such as API keys shared across a team, you can set secrets at the level of the repository or organization. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)."
@@ -58,7 +58,7 @@ Alternatively, for secrets that the owner of the repository or organization can
```
1. Add a property within `secrets` for each secret you want to recommend. For example, change `NAME_OF_SECRET_1` and `NAME_OF_SECRET_2`, in the previous code example, to the names of the secrets that people should create in their personal settings for {% data variables.product.prodname_codespaces %}.
1. Optionally, supply a description for each secret and a URL for more information about this secret.
1. Optionally, supply a description for each secret and a URL for more information about this secret.
You can omit `description` and `documentationUrl`, as shown by `NAME_OF_SECRET_2` in the previous code example.