|
1 | 1 | # Contributing |
2 | 2 |
|
3 | | -When contributing to this repository, please first discuss the change you wish to make via [issues](https://github.com/onlook-dev/onlook/issues), |
4 | | -[Discord](https://discord.gg/hERDfFZCsH), [email](mailto:contact@onlook.com), or any other method with the owners of this repository before making a change. |
| 3 | +When contributing to this repository, please first discuss the change you wish |
| 4 | +to make via [issues](https://github.com/onlook-dev/desktop/issues), |
| 5 | +[Discord](https://discord.gg/hERDfFZCsH), [email](mailto:contact@onlook.com), or |
| 6 | +any other method with the owners of this repository before making a change. |
5 | 7 |
|
6 | | -Please note we have a [code of conduct](./CODE_OF_CONDUCT.md), please follow it in all your interactions with the project. |
| 8 | +Please note we have a [code of conduct](./CODE_OF_CONDUCT.md), please follow it |
| 9 | +in all your interactions with the project. |
7 | 10 |
|
8 | 11 | ## Pull Request Process |
9 | 12 |
|
10 | | -1. To create a Pull Request (PR), [create a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) of the project. |
| 13 | +1. To create a Pull Request (PR), |
| 14 | + [create a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) |
| 15 | + of the project. |
11 | 16 |
|
12 | 17 |  |
13 | 18 |
|
14 | | -2. Create your changes in your fork and [open a PR from that fork.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) |
| 19 | +2. Create your changes in your fork and |
| 20 | + [open a PR from that fork.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) |
15 | 21 |
|
16 | 22 |  |
17 | 23 |
|
18 | | -3. Update the PR description with details of the changes. Link the issue if relevant. |
19 | | -4. Request a review of one of the maintainers. Once accepted, they will be able to merge your PR. |
| 24 | +3. Update the PR description with details of the changes. Link the issue if |
| 25 | + relevant. |
| 26 | +4. Request a review of one of the maintainers. Once accepted, they will be able |
| 27 | + to merge your PR. |
20 | 28 |
|
21 | 29 | ## Style guide |
22 | 30 |
|
23 | | -We try to follow guidelines from [Clean Code](https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988cf8d29) and the boy scoute rule: |
| 31 | +We try to follow guidelines from |
| 32 | +[Clean Code](https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988cf8d29) |
| 33 | +and the boy scoute rule: |
24 | 34 |
|
25 | | -"Leave the code cleaner, not messier, than how you found it". |
| 35 | +"Leave the code cleaner, not messier, than how you found it". |
0 commit comments