Skip to content

Commit 57d47a0

Browse files
hubwriterhubwriter
authored
Codespaces: change 'encrypted secrets' to 'secrets' (github#41416)
1 parent bec13b6 commit 57d47a0

File tree

57 files changed

+111
-105
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

57 files changed

+111
-105
lines changed

‎content/actions/automating-builds-and-tests/about-continuous-integration.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,8 @@ For a definition of common terms, see "[AUTOTITLE](/actions/learn-github-actions
5050

5151
Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
5252

53+
{% ifversion fpt or ghec %}
5354
## Further reading
5455

55-
{% ifversion fpt or ghec %}
5656
- "[AUTOTITLE](/billing/managing-billing-for-github-actions)"
5757
{% endif %}

‎content/actions/automating-builds-and-tests/building-and-testing-nodejs.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ steps:
206206

207207
{% data reusables.actions.setup-node-intro %}
208208

209-
To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
209+
To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
210210

211211
In the example below, the secret `NPM_TOKEN` stores the npm authentication token. The `setup-node` action configures the _.npmrc_ file to read the npm authentication token from the `NODE_AUTH_TOKEN` environment variable. When using the `setup-node` action to create an _.npmrc_ file, you must set the `NODE_AUTH_TOKEN` environment variable with the secret that contains your npm authentication token.
212212

‎content/actions/automating-builds-and-tests/building-and-testing-powershell.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@ The `always()` function configures the job to continue processing even if there
227227

228228
## Publishing to PowerShell Gallery
229229

230-
You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use secrets to store any tokens or credentials needed to publish your package. For more information, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
230+
You can configure your workflow to publish your PowerShell module to the PowerShell Gallery when your CI tests pass. You can use secrets to store any tokens or credentials needed to publish your package. For more information, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
231231

232232
The following example creates a package and uses `Publish-Module` to publish it to the PowerShell Gallery:
233233

‎content/actions/automating-builds-and-tests/building-and-testing-python.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -377,7 +377,7 @@ jobs:
377377

378378
You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This section demonstrates how you can use {% data variables.product.prodname_actions %} to upload your package to PyPI each time you [publish a release](/repositories/releasing-projects-on-github/managing-releases-in-a-repository).
379379

380-
For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
380+
For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
381381

382382
```yaml copy
383383
{% data reusables.actions.actions-not-certified-by-github-comment %}

‎content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
7575
7676
1. Create {% data variables.product.prodname_actions %} secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to store the values for your Amazon IAM access key.
7777
78-
For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
78+
For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository)."
7979
8080
See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials.
8181

‎content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ $ gcloud services enable \
6666

6767
### Configuring a service account and storing its credentials
6868

69-
This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
69+
This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded {% ifversion fpt or ghec %}encrypted {% endif %}repository secret named `GKE_SA_KEY`.
7070

7171
1. Create a new service account:
7272

@@ -112,11 +112,11 @@ This procedure demonstrates how to create the service account for your GKE integ
112112
export GKE_SA_KEY=$(cat key.json | base64)
113113
```
114114

115-
For more information about how to store a secret, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
115+
For more information about how to store a secret, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
116116

117117
### Storing your project name
118118

119-
Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
119+
Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
120120

121121
### (Optional) Configuring kustomize
122122

‎content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ You should have an understanding of Xcode app building and signing. For more inf
3535

3636
The signing process involves storing certificates and provisioning profiles, transferring them to the runner, importing them to the runner's keychain, and using them in your build.
3737

38-
To use your certificate and provisioning profile on a runner, we strongly recommend that you use {% data variables.product.prodname_dotcom %} secrets. For more information on creating secrets and using them in a workflow, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
38+
To use your certificate and provisioning profile on a runner, we strongly recommend that you use {% data variables.product.prodname_dotcom %} secrets. For more information on creating secrets and using them in a workflow, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
3939

4040
Create secrets in your repository or organization for the following items:
4141

‎content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ Once custom deployment protection rules have been created and installed on a rep
125125

126126
## Environment secrets
127127

128-
Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."
128+
Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions)."
129129

130130
{% ifversion fpt %}
131131
{% note %}

‎content/actions/examples/using-the-github-cli-on-a-runner.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ jobs:
7676
if: github.repository == 'github/docs-internal'
7777
# Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
7878
runs-on: ubuntu-latest
79-
# Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
79+
# Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/using-secrets-in-github-actions). These variables will be referenced later in the workflow.
8080
env:
8181
GITHUB_TOKEN: {% raw %}${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}{% endraw %}
8282
FIRST_RESPONDER_PROJECT: Docs content first responder

‎content/actions/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ featuredLinks:
2525
- /actions/learn-github-actions/contexts
2626
- /actions/learn-github-actions/expressions
2727
- /actions/learn-github-actions/variables
28-
- /actions/security-guides/encrypted-secrets
28+
- /actions/security-guides/using-secrets-in-github-actions
2929
changelog:
3030
label: actions
3131
redirect_from:

0 commit comments

Comments
 (0)