Skip to content

Commit 35f8595

Browse files
committed
style: do not put every sentence on a separate line
1 parent db6cc06 commit 35f8595

File tree

1 file changed

+3
-12
lines changed

1 file changed

+3
-12
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -82,11 +82,7 @@ Over time, we should track which items are useful and which don't get any traffi
8282
## Installation and setup
8383

8484
1. Use Git to clone this repository.
85-
2. If you work at Apify and can install packages prefixed with `@apify-packages`, you can skip this step.
86-
Otherwise go to GitHub and navigate to [Settings / Personal access tokens / Tokens (classic)](https://github.com/settings/tokens).
87-
Despite the UI suggesting you should use the new fine-grained tokens, generate a **classic token** with scopes **repo** and **write:packages**.
88-
Keep the token somewhere safe.
89-
Then run the following command and use your GitHub username together with the token as credentials:
85+
2. If you work at Apify and can install packages prefixed with `@apify-packages`, you can skip this step. Otherwise go to GitHub and navigate to [Settings / Personal access tokens / Tokens (classic)](https://github.com/settings/tokens). Despite the UI suggesting you should use the new fine-grained tokens, generate a **classic token** with scopes **repo** and **write:packages**. Keep the token somewhere safe. Then run the following command and use your GitHub username together with the token as credentials:
9086

9187
```bash
9288
npm login --scope=@apify-packages --registry=https://npm.pkg.github.com --auth-type=legacy
@@ -96,18 +92,13 @@ Over time, we should track which items are useful and which don't get any traffi
9692
3. Run `npm install`.
9793
4. Run `npm start`. The website should open at <http://localhost:3000>.
9894

99-
This is sufficient to work on the main content, i.e. the Academy and Platform docs.
100-
If you want to also work on the other parts of the docs, you may want to first join them all together using Nginx.
95+
This is sufficient to work on the main content, i.e. the Academy and Platform docs. If you want to also work on the other parts of the docs, you may want to first join them all together using Nginx.
10196

10297
### Join all the docs repos together using Nginx
10398

10499
By default, the parts of the docs sourced from other repositories will give you 404s. If you need to locally run the project with all the other repositories included, clone them all and setup an Nginx server according to the steps below.
105100

106-
For the setup to work, use `npm start:dev` instead of `npm start` when starting `apify-docs`.
107-
This causes all links in the top navigation and the footer to be absolute.
108-
They will now use `docs.apify.loc` as a host.
109-
Clone all the remaining docs repositories, and start their Docusaurus instances.
110-
To run Docusaurus on a specific port, use `npm start -- --port XXXX`.
101+
For the setup to work, use `npm start:dev` instead of `npm start` when starting `apify-docs`. This causes all links in the top navigation and the footer to be absolute. They will now use `docs.apify.loc` as a host. Clone all the remaining docs repositories, and start their Docusaurus instances. To run Docusaurus on a specific port, use `npm start -- --port XXXX`.
111102

112103
| repo | port |
113104
|---------------------|------|

0 commit comments

Comments
 (0)