|
1 | | -## Description |
| 1 | +<!-- |
2 | 2 |
|
3 | | -Please explain the changes you made here. |
| 3 | +Thanks for submitting a pull request! Please follow these guidelines: |
4 | 4 |
|
5 | | -## Checklist |
| 5 | +- Title your PR starting with `fix:`, `feat:`, `chore:`, etc. See https://www.conventionalcommits.org for details. |
| 6 | +- Provide a brief description of your PR. Explain anything not obvious. |
| 7 | +- Add an entry to the top of the changelog and include it in your PR. |
| 8 | +- Include tests in your PR whenever possible. |
6 | 9 |
|
7 | | -All PRs should check the following boxes: |
| 10 | +You can delete these instructions. |
8 | 11 |
|
9 | | -- [ ] I have given this PR a title using the |
10 | | - [Conventional Commits](https://www.conventionalcommits.org/) syntax, leading with `fix:`, |
11 | | - `feat:`, `chore:`, `ci:`, etc. |
12 | | - - The title should also be used for the commit message when the PR is squashed and merged. |
13 | | -- [ ] I have formatted and linted my code with Trunk, per the instructions in |
14 | | - [the contributing guide](https://github.com/hypermodeinc/modus/blob/main/CONTRIBUTING.md#trunk). |
15 | | - |
16 | | -If the PR includes a _code change_, then also check the following boxes. _(If not, then delete the |
17 | | -next section.)_ |
18 | | - |
19 | | -- [ ] I have added an entry to the `CHANGELOG.md` file. |
20 | | - - Add to the "UNRELEASED" section at the top of the file, creating one if it doesn't yet exist. |
21 | | - - Be sure to include the link to this PR, and please sort the section numerically by PR number. |
22 | | -- [ ] I have manually tested the new or modified code, and it appears to behave correctly. |
23 | | -- [ ] I have added or updated unit tests where appropriate, if applicable. |
| 12 | +--> |
0 commit comments