|
| 1 | +--- |
| 2 | +applyTo: '**' |
| 3 | +--- |
| 4 | + |
| 5 | +Always ask for PR target branch(upstream), and the allowed targets branches are "development" and "main" branch |
| 6 | +Always ask for the commits to be added to the PR in comma separated format and display the most reset commits using the following format: |
| 7 | +`<commit id>: <commit title or message>` |
| 8 | +Analyze the selected commits by id when generating the PR description |
| 9 | +PR title must be a summary of all the selected commit messages with emoji |
| 10 | +PR description must be generated as MD code snippet |
| 11 | +Always Use the following template when generating PR(Pull Request) description |
| 12 | + |
| 13 | +```md |
| 14 | +# <Pull request title that best summaries the changes and the type of changes made with the appropriate emoji> |
| 15 | + |
| 16 | +| Status | Type | Env Vars Change | |
| 17 | +| :--------: | :---------------------------------: | :-------------: | |
| 18 | +| Ready/Hold | Feature/Bug/Tooling/Refactor/Hotfix | Yes/No | |
| 19 | + |
| 20 | +> ⚠️ NOTE: <OPTIONAL: use notes like this to emphasize something about the PR. This could include other PRs this PR is built on top of; reasons for why the PR is on hold; or anything else you would like to draw attention to.> |
| 21 | +
|
| 22 | +## Problem |
| 23 | + |
| 24 | +<What problem are you trying to solve?> |
| 25 | + |
| 26 | +- problem 1 |
| 27 | +- problem 2 |
| 28 | + .... |
| 29 | + |
| 30 | +## Solution |
| 31 | + |
| 32 | +<How did you solve the problem?> |
| 33 | + |
| 34 | +- solution 1 |
| 35 | +- solution 2 |
| 36 | + .... |
| 37 | + |
| 38 | +## Test results |
| 39 | + |
| 40 | +<This can be a list of links to test results or a description of the tests run or some UI screenshots of the new/updated feature. |
| 41 | +If don't found any data relate, give exactly instruction "_Add your screenshots or recording about testing_" instead of "**NEED FILL**"> |
| 42 | + |
| 43 | +## Other changes <e.g. bug fixes, UI tweaks, small refactors> |
| 44 | + |
| 45 | +- change 1 |
| 46 | +- change 2 |
| 47 | + .... |
| 48 | + |
| 49 | +## Deploy Notes |
| 50 | + |
| 51 | +<Notes regarding deployment of the contained body of work. These should note any new dependencies, new scripts, etc. |
| 52 | +If no have new info, only show exactly "_There are no new dependencies, scripts, or environment variables introduced with this PR_"> |
| 53 | + |
| 54 | +<OPTIONAL: (IMPORTANT) delete this field if don't have new environment variables> |
| 55 | +**New environment variables **: |
| 56 | + |
| 57 | +- `env var` : env var details |
| 58 | + |
| 59 | +<OPTIONAL: (IMPORTANT) delete this field if don't have new scripts> |
| 60 | +**New scripts**: |
| 61 | + |
| 62 | +- `script` : script (DB migrations, etc) details |
| 63 | + |
| 64 | +<OPTIONAL: (IMPORTANT) delete this field if don't have new dependencies> |
| 65 | +**New dependencies**: |
| 66 | + |
| 67 | +- `dependency` : dependency details |
| 68 | + |
| 69 | +<OPTIONAL: (IMPORTANT) delete this field if don't have new dev dependencies> |
| 70 | +**New dev dependencies**: |
| 71 | + |
| 72 | +- `dependency` : dependency details |
| 73 | +``` |
0 commit comments