forked from Avaiga/taipy
-
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.
chore: add PR template (Avaiga#2193)
Co-authored-by: Joao Andre <joaoandre.ja@gmail.com>
- Loading branch information
1 parent
b64ed1f
commit c5f76d1
Showing
1 changed file
with
40 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,40 @@ | ||
## What type of PR is this? (check all applicable) | ||
|
||
- [ ] Refactor | ||
- [ ] Feature | ||
- [ ] Bug Fix | ||
- [ ] Optimization | ||
- [ ] Documentation Update | ||
|
||
## Description | ||
|
||
## Related Tickets & Documents | ||
|
||
<!-- | ||
For pull requests that relate or close an issue, please include them | ||
below. We like to follow [Github's guidance on linking issues to pull requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue). | ||
For example having the text: "closes #1234" would connect the current pull | ||
request to issue 1234. And when we merge the pull request, Github will | ||
automatically close the issue. | ||
--> | ||
|
||
- Related Issue # | ||
- Closes # | ||
|
||
## How to reproduce the issue | ||
|
||
_Please replace this line with instructions on how to reproduce the issue or test the feature._ | ||
|
||
## Other branches or releases that this needs to be backported | ||
_Describe which projects this change will impact and that needs to be backported._ | ||
|
||
## Checklist | ||
_We encourage you to keep the code coverage percentage at 80% and above._ | ||
|
||
- [ ] Does this solution meet the acceptance criteria of the related issue? | ||
- [ ] Is the related issue checklist completed? | ||
- [ ] Does this PR adds unit tests for the developed code? If not, why? | ||
- [ ] End-to-End tests have been added or updated? | ||
- [ ] Was the documentation updated, or a dedicated issue for documentation created? (If applicable) | ||
- [ ] Is the release notes updated? (If applicable) |