-
Notifications
You must be signed in to change notification settings - Fork 394
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
16 additions
and
38 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,43 +1,21 @@ | ||
| <!-- Thank you for contributing to Sanity. Please read our [Code of Conduct](https://github.com/sanity-io/sanity/blob/next/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/sanity-io/sanity/blob/next/CONTRIBUTING.md) before submitting a PR. | ||
| ### Description | ||
|
|
||
| To help us review your Pull Request, please make sure you follow the steps and guidelines below. | ||
| <!-- | ||
| What changes are introduced? | ||
| Why are these changes introduced? | ||
| What issue(s) does this solve? (with link, if possible) | ||
| --> | ||
|
|
||
| It's OK to open a Pull Request to start a discussion/ask for help, but it should then be created as a [Draft Pull Request](https://github.blog/2019-02-14-introducing-draft-pull-requests/). | ||
| ### What to review | ||
|
|
||
| Do not delete the instructional comments. --> | ||
| <!-- | ||
| What steps should the reviewer take in order to review? | ||
| What parts/flows of the application/packages/tooling is affected? | ||
| Add a test script, if that makes sense. | ||
| --> | ||
|
|
||
| **Type of change (check at least one)** | ||
| ### Notes for release | ||
|
|
||
| - [ ] Bug fix (non-breaking change which fixes an issue) | ||
| - [ ] New feature (non-breaking change which adds functionality) | ||
| - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) | ||
| - [ ] Documentation (fix or update to documentation) | ||
| - [ ] Maintenance | ||
| - [ ] Other, please describe: | ||
|
|
||
| **Does this change require a documentation update? (Check one)** | ||
|
|
||
| - [ ] Yes | ||
| - [ ] No | ||
|
|
||
| **Current behavior** | ||
|
|
||
| <!-- Reference/link the relevant issue and/or describe the behavior. --> | ||
|
|
||
| **Description** | ||
|
|
||
| <!-- Please include a summary of the changes this PR introduces and/or which issue is fixed. Please also include relevant motivation and context of why this PR is necessary. --> | ||
|
|
||
| **Note for release** | ||
|
|
||
| <!-- Please include a high level summary of the changes this PR introduce. The intended audience is both editors and developers. If it's introducing a new feature, remember to link to docs/blogpost, if it's a bugfix, please describe the bug in non-technical terms (e.g. how a user/developer may have experienced it). | ||
| For inspiration, check out the release notes from an earlier release: https://github.com/sanity-io/sanity/releases/tag/v0.142.0 --> | ||
|
|
||
| **Checklist** | ||
|
|
||
| - [ ] I have read the [Contributing Guidelines](https://github.com/sanity-io/sanity/blob/next/CONTRIBUTING.md) | ||
| - [ ] The PR title includes a link to the relevant issue | ||
| - [ ] The PR title is appropriately formatted: `[some-package] PR title (#123)` | ||
| - [ ] The code is linted | ||
| - [ ] The test suite is passing | ||
| - [ ] Corresponding changes to the documentation have been made | ||
| <!-- | ||
| A description of the change(s) that should be used in the release notes. | ||
| --> |