forked from flutter/plugins
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add pull request template (flutter#1375)
- Loading branch information
1 parent
81a5995
commit 2f776ac
Showing
1 changed file
with
37 additions
and
0 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 |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| ## Description | ||
|
|
||
| *Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.* | ||
|
|
||
| ## Related Issues | ||
|
|
||
| *Replace this paragraph with a list of issues related to this PR from the [issue database](https://github.com/flutter/flutter/issues). Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.* | ||
|
|
||
| ## Checklist | ||
|
|
||
| Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (`[x]`). This will ensure a smooth and quick review process. | ||
|
|
||
| - [ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. | ||
| - [ ] My PR includes unit or integration tests for *all* changed/updated/fixed behaviors (See [Contribution Guide]). | ||
| - [ ] All existing and new tests are passing. | ||
| - [ ] I updated/added relevant documentation (doc comments with `///`). | ||
| - [ ] The analyzer (`flutter analyze`) does not report any problems on my PR. | ||
| - [ ] I read and followed the [Flutter Style Guide]. | ||
| - [ ] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences] | ||
| - [ ] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy]. | ||
| - [ ] I updated CHANGELOG.md to add a description of the change. | ||
| - [ ] I signed the [CLA]. | ||
| - [ ] I am willing to follow-up on review comments in a timely manner. | ||
|
|
||
| ## Breaking Change | ||
|
|
||
| Does your PR require plugin user to manually update their apps to accommodate your change? | ||
|
|
||
| - [ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision). | ||
| - [ ] No, this is *not* a breaking change. | ||
|
|
||
| <!-- Links --> | ||
| [issue database]: https://github.com/flutter/flutter/issues | ||
| [Contributor Guide]: https://github.com/flutter/plugins/blob/master/CONTRIBUTING.md | ||
| [Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo | ||
| [pub versioning philosophy]: https://www.dartlang.org/tools/pub/versioning | ||
| [CLA]: https://cla.developers.google.com/ |