You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: fix invalid link and unify link presentation (npm#76)
* docs: fix invalid link and unify link presentation
There was an invalid link on 'automation token' which leads to 404, also not unified style of link presentation because other links have quotes.
* Update content/integrations/integrating-npm-with-external-services/using-private-packages-in-a-ci-cd-workflow.mdx
Co-authored-by: Gar <[email protected]>
* docs: fix unnecessary quotes around link
* Update content/integrations/integrating-npm-with-external-services/using-private-packages-in-a-ci-cd-workflow.mdx
Co-authored-by: Jordan Harband <[email protected]>
Co-authored-by: Gar <[email protected]>
Co-authored-by: Jordan Harband <[email protected]>
Copy file name to clipboardExpand all lines: content/integrations/integrating-npm-with-external-services/using-private-packages-in-a-ci-cd-workflow.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ For more information on creating access tokens, including CIDR-whitelisted token
22
22
23
23
### Continuous deployment
24
24
25
-
Since continuous deployment environments usually involve the creation of a deploy artifact, you may wish to create an [automation token](create-token#creating-tokens-on-the-website) on the website. This will allow you to publish even if you have two-factor authentication enabled on your account.
25
+
Since continuous deployment environments usually involve the creation of a deploy artifact, you may wish to create an [automation token][create-token] on the website. This will allow you to publish even if you have two-factor authentication enabled on your account.
26
26
27
27
### Interactive workflows
28
28
@@ -47,13 +47,13 @@ Example:
47
47
npm token create --cidr=192.0.2.0/24
48
48
```
49
49
50
-
For more information, see "[Creating and viewing authentication tokens](creating-and-viewing-access-tokens)".
50
+
For more information, see "[Creating and viewing authentication tokens][create-token]".
51
51
52
52
## Set the token as an environment variable on the CI/CD server
53
53
54
54
Set your token as an environment variable, or a secret, in your CI/CD server.
55
55
56
-
For example, in GitHub Actions, you would [add your token as a secret](https://docs.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets). Then you can make the secret available to workflows.
56
+
For example, in GitHub Actions, you would [add your token as a secret](https://docs.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets). Then you can make the secret available to workflows.
57
57
58
58
If you named the secret `NPM_TOKEN`, then you would want to create an environment variable named `NPM_TOKEN` from that secret.
59
59
@@ -77,14 +77,14 @@ Use a project-specific `.npmrc` file with a variable for your token to securely
77
77
//registry.npmjs.org/:_authToken=${NPM_TOKEN}
78
78
```
79
79
80
-
**Note:** that you are specifying a literal value of `${NPM_TOKEN}`. The npm cli will replace this value with the contents of the `NPM_TOKEN` environment variable. Do **not** put a token in this file.
80
+
**Note:** that you are specifying a literal value of `${NPM_TOKEN}`. The npm cli will replace this value with the contents of the `NPM_TOKEN` environment variable. Do **not** put a token in this file.
81
81
82
82
2. Check in the `.npmrc` file.
83
83
84
84
## Securing your token
85
85
86
-
Your token may have permission to read private packages, publish new packages on your behalf, or change user or package settings. Protect your token.
86
+
Your token may have permission to read private packages, publish new packages on your behalf, or change user or package settings. Protect your token.
87
87
88
-
Do not add your token to version control or store it insecurely. Store it in a package manager, your cloud provider's secure storage, or your CI/CD provider's secure storage.
88
+
Do not add your token to version control or store it insecurely. Store it in a package manager, your cloud provider's secure storage, or your CI/CD provider's secure storage.
0 commit comments