flutter/flame
1
0
Fork 0
mirror of https://github.com/flame-engine/flame.git synced 2025-11-07 23:17:19 +08:00
Code Issues Packages Projects Releases Wiki Activity

chore: commented out PR template sections (#1412)

Browse Source
This commit is contained in:
Alejandro Santiago
2022-03-02 10:14:19 +00:00
committed by GitHub
parent 4dc65f1253
commit ada5740d05
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
.github/pull_request_template.md vendored
View File

@ -1,14 +1,14 @@
# Description # Description
*Replace this paragraph with a description of what this PR is doing. <!-- Provide a description of what this PR is doing.
If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, If you're modifying existing behavior, describe the existing behavior, how this PR is changing it,
and what motivated the change. If this is a breaking change, specify explicitly which APIs have been and what motivated the change. If this is a breaking change, specify explicitly which APIs have been
changed.* changed. -->
## Checklist ## Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the <!-- 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. relevant checkboxes (`[x]`). This will ensure a smooth and quick review process. -->
- [ ] The title of my PR starts with a [Conventional Commit] prefix (`fix:`, `feat:`, `docs:` etc). - [ ] The title of my PR starts with a [Conventional Commit] prefix (`fix:`, `feat:`, `docs:` etc).
- [ ] I have read the [Contributor Guide] and followed the process outlined for submitting PRs. - [ ] I have read the [Contributor Guide] and followed the process outlined for submitting PRs.
@ -18,16 +18,18 @@ relevant checkboxes (`[x]`). This will ensure a smooth and quick review process.
## Breaking Change ## Breaking Change
Does your PR require Flame users to manually update their apps to accommodate your change? <!-- Does your PR require Flame users to manually update their apps to accommodate your change?
- [ ] Yes, this is a breaking change. (Indicate it in the [Conventional Commit] prefix with a `!`, If the PR is a breaking change this should be indicated with suffix "!" (for example, `feat!:`, `fix!:`). See [Conventional Commit] for details.
e.g. `feat!:`, `fix!:`). -->
- [ ] Yes, this is a breaking change.
- [ ] No, this is *not* a breaking change. - [ ] No, this is *not* a breaking change.
## Related Issues ## Related Issues
*Replace this paragraph with a list of issues related to this PR from the [issue database]. <!-- Provide a list of issues related to this PR from the [issue database].
Indicate which of these issues are resolved or fixed by this PR, i.e. Fixes #xxxx* Indicate which of these issues are resolved or fixed by this PR, i.e. Fixes #xxxx* !-->
<!-- Links --> <!-- Links -->
[issue database]: https://github.com/flame-engine/flame/issues [issue database]: https://github.com/flame-engine/flame/issues