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
Copy file name to clipboardExpand all lines: README.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,19 @@ cd documentation
59
59
We use the [gatsby-remark-embed-snippet](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-remark-embed-snippet) to use files from GitHub in our docs. Before you can build a local development site, you need to provide a GitHub token to the environment:
60
60
61
61
1. Log in to GitHub and go to <https://github.com/settings/tokens>
62
-
1. Click **Generate new token**
62
+
1. Click **Generate new token**.
63
+
1. Give the token a name, expiration, and description.
64
+
1. Select your GitHub user as the resource owner.
65
+
1. For repository access, select**Onlyselectrepositories** and selectyour fork of this repository.
66
+
1. Under Repository permissions, choose **Access: Read-only** from the **Access** dropdown button.
67
+
1. Click **Generate token**.
68
+
69
+
#### GitHub Tokens (classic)
70
+
71
+
Alternatively, if you'd rather create a classic-style token:
72
+
73
+
1. Log in to GitHub and go to <https://github.com/settings/tokens>
74
+
1. Click **Generate new token (classic)**
63
75
1. Give the token a name and click the **public_repo** checkbox, then the **Generate Token** button at the bottom
64
76
1. Copy the token to your clipboard
65
77
1. In the root `documentation` directory, create a new file called `.env.development` and add (replacing `$TOKENHASH` ):
@@ -81,7 +93,7 @@ npm ci
81
93
Still in the `documentation` directory:
82
94
83
95
```bash
84
-
npm run develop
96
+
npm start
85
97
```
86
98
87
99
Use your local browser to navigate to `localhost:8000/`.
0 commit comments