|
4 | 4 | > By interacting with this repository, organization, or community you agree to |
5 | 5 | > abide by its terms. |
6 | 6 |
|
7 | | -Hi! 👋 |
| 7 | +Hi! |
| 8 | +👋 |
8 | 9 | We’re excited that you’re interested in contributing! |
9 | 10 | Take a moment to read the following guidelines. |
10 | | -And thanks for contributing to **unified**! 👏👌✨ |
| 11 | +And thanks for contributing to **unified**! |
| 12 | +👏👌✨ |
11 | 13 |
|
12 | 14 | If you’re raising an issue, please understand that people involved with this |
13 | 15 | project often do so for fun, next to their day job; you are not entitled to |
14 | 16 | free customer service. |
15 | 17 |
|
16 | 18 | ## Contents |
17 | 19 |
|
18 | | -* [Ecosystem](#ecosystem) |
19 | | -* [Contributions](#contributions) |
20 | | - * [Financial support](#financial-support) |
21 | | - * [Improve documentation](#improve-documentation) |
22 | | - * [Improve issues](#improve-issues) |
23 | | - * [Give feedback on issues](#give-feedback-on-issues) |
24 | | - * [Write code](#write-code) |
25 | | -* [Support](#support) |
26 | | -* [Submitting an issue](#submitting-an-issue) |
27 | | -* [Submitting a pull request](#submitting-a-pull-request) |
28 | | -* [Resources](#resources) |
29 | | -* [License](#license) |
| 20 | +* [Ecosystem](#ecosystem) |
| 21 | +* [Contributions](#contributions) |
| 22 | + * [Financial support](#financial-support) |
| 23 | + * [Improve documentation](#improve-documentation) |
| 24 | + * [Improve issues](#improve-issues) |
| 25 | + * [Give feedback on issues](#give-feedback-on-issues) |
| 26 | + * [Write code](#write-code) |
| 27 | +* [Support](#support) |
| 28 | +* [Submitting an issue](#submitting-an-issue) |
| 29 | +* [Submitting a pull request](#submitting-a-pull-request) |
| 30 | +* [Resources](#resources) |
| 31 | +* [License](#license) |
30 | 32 |
|
31 | 33 | ## Ecosystem |
32 | 34 |
|
@@ -79,35 +81,35 @@ See [`support.md`][support] on how to get help. |
79 | 81 |
|
80 | 82 | ## Submitting an issue |
81 | 83 |
|
82 | | -* The issue tracker is for issues. |
83 | | - See [`support.md`][support] on how to get help. |
84 | | -* Search the issue tracker (including closed issues) before opening a new |
85 | | - issue |
86 | | -* Ensure you’re using the latest version of projects |
87 | | -* Use a clear and descriptive title |
88 | | -* Include as much information as possible: steps to reproduce the issue, |
89 | | - error message, version, operating system, etcetera |
90 | | -* The more time you put into an issue, the more we will |
91 | | -* The best issue report is a [failing test][unit-test] proving it |
| 84 | +* The issue tracker is for issues. |
| 85 | + See [`support.md`][support] on how to get help. |
| 86 | +* Search the issue tracker (including closed issues) before opening a new |
| 87 | + issue |
| 88 | +* Ensure you’re using the latest version of projects |
| 89 | +* Use a clear and descriptive title |
| 90 | +* Include as much information as possible: steps to reproduce the issue, |
| 91 | + error message, version, operating system, etcetera |
| 92 | +* The more time you put into an issue, the more we will |
| 93 | +* The best issue report is a [failing test][unit-test] proving it |
92 | 94 |
|
93 | 95 | ## Submitting a pull request |
94 | 96 |
|
95 | | -* Non-trivial changes are often best discussed in an issue first, to prevent |
96 | | - you from doing unnecessary work |
97 | | -* For ambitious tasks, you should try to get your work in front of the |
98 | | - community for feedback as soon as possible |
99 | | -* New features should be accompanied with tests and documentation |
100 | | -* Don’t include unrelated changes |
101 | | -* Lint and test before submitting code by running `$ npm test` |
102 | | -* Write a convincing description of why we should land your pull request: |
103 | | - it’s your job to convince us |
| 97 | +* Non-trivial changes are often best discussed in an issue first, to prevent |
| 98 | + you from doing unnecessary work |
| 99 | +* For ambitious tasks, you should try to get your work in front of the |
| 100 | + community for feedback as soon as possible |
| 101 | +* New features should be accompanied with tests and documentation |
| 102 | +* Don’t include unrelated changes |
| 103 | +* Lint and test before submitting code by running `$ npm test` |
| 104 | +* Write a convincing description of why we should land your pull request: |
| 105 | + it’s your job to convince us |
104 | 106 |
|
105 | 107 | ## Resources |
106 | 108 |
|
107 | | -* [How to contribute to open source](https://opensource.guide/how-to-contribute/) |
108 | | -* [Making your first contribution](https://medium.com/@vadimdemedes/making-your-first-contribution-de6576ddb190) |
109 | | -* [Using pull requests](https://help.github.com/articles/about-pull-requests/) |
110 | | -* [GitHub help](https://help.github.com) |
| 109 | +* [How to contribute to open source](https://opensource.guide/how-to-contribute/) |
| 110 | +* [Making your first contribution](https://medium.com/@vadimdemedes/making-your-first-contribution-de6576ddb190) |
| 111 | +* [Using pull requests](https://help.github.com/articles/about-pull-requests/) |
| 112 | +* [GitHub help](https://help.github.com) |
111 | 113 |
|
112 | 114 | ## License |
113 | 115 |
|
|
0 commit comments