|
2 | 2 |
|
3 | 3 | 🎉 Thanks for considering contributing to this project! 🎉
|
4 | 4 |
|
5 |
| -These guidelines will help you send a pull request. |
| 5 | +When contributing to this repository, please first discuss the change you wish to make via an |
| 6 | +[issue](https://github.com/netlify/next-runtime/issues/new/choose). Please use the issue templates. They are there to |
| 7 | +help you and to help the maintainers gather information. |
6 | 8 |
|
7 |
| -If you're submitting an issue instead, please skip this document. |
| 9 | +Before working on an issue, ask to be assigned to it. This makes it clear to other potential contributors that someone |
| 10 | +is working on the issue. |
8 | 11 |
|
9 |
| -If your pull request is related to a typo or the documentation being unclear, please click on the relevant page's `Edit` |
10 |
| -button (pencil icon) and directly suggest a correction instead. |
| 12 | +When creating a PR, please use the template. The information in the template helps maintainers review your pull request.``` |
11 | 13 |
|
12 | 14 | This project was made with ❤️. The simplest way to give back is by starring and sharing it online.
|
13 | 15 |
|
@@ -37,9 +39,9 @@ We use [Conventional Commit messages](https://www.conventionalcommits.org/) to a
|
37 | 39 |
|
38 | 40 | Most common commit message prefixes are:
|
39 | 41 |
|
40 |
| -* `fix:` which represents bug fixes, and generate a patch release. |
41 |
| -* `feat:` which represents a new feature, and generate a minor release. |
42 |
| -* `feat!:`, `fix!:` or `refactor!:` and generate a major release. |
| 42 | +- `fix:` which represents bug fixes, and generate a patch release. |
| 43 | +- `feat:` which represents a new feature, and generate a minor release. |
| 44 | +- `feat!:`, `fix!:` or `refactor!:` and generate a major release. |
43 | 45 |
|
44 | 46 | ## Releasing
|
45 | 47 |
|
|
0 commit comments