-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[opt](pr-template) optimize the PR template (#43444)
### What problem does this PR solve? Problem Summary: Simplify the PR template, move the check list to the auto response section.
- Loading branch information
1 parent
acea8fc
commit 8deb61f
Showing
1 changed file
with
11 additions
and
40 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,63 +1,34 @@ | ||
### What problem does this PR solve? | ||
<!-- | ||
You need to clearly describe your PR in this part: | ||
You need to clearly describe your PR in this section: | ||
1. What problem was fixed (it's best to include specific error reporting information). How it was fixed. | ||
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be. | ||
3. What features were added. Why this function was added. | ||
4. Which codes were refactored and why this part of the code was refactored. | ||
5. Which functions were optimized and what is the difference before and after the optimization. | ||
3. What features were added. Why was this function added? | ||
4. Which code was refactored and why was this part of the code refactored? | ||
5. Which functions were optimized and what is the difference before and after the optimization? | ||
The description of the PR needs to enable reviewers to quickly and clearly understand the logic of the code modification. | ||
--> | ||
|
||
<!-- | ||
If there are related issues, please fill in the issue number. | ||
- If you want the issue to be closed after the PR is merged, please use "close #12345". Otherwise, use "ref #12345" | ||
- If you want the issue to be closed after the PR is merged, please use "close #12345". Otherwise, use "ref #12345". | ||
--> | ||
Issue Number: close #xxx | ||
|
||
<!-- | ||
If this PR is followup a preivous PR, for example, fix the bug that introduced by a related PR, | ||
link the PR here | ||
If this PR is a follow-up to a previous PR, for example, to fix a bug introduced by a related PR, | ||
link the PR here. | ||
--> | ||
Related PR: #xxx | ||
|
||
Problem Summary: | ||
|
||
### Check List (For Author) | ||
|
||
- Test <!-- At least one of them must be included. --> | ||
### Release note | ||
|
||
- [ ] Regression test | ||
- [ ] Unit Test | ||
- [ ] Manual test (add detailed scripts or steps below) | ||
- [ ] No need to test or manual test. Explain why: | ||
- [ ] This is a refactor/code format and no logic has been changed. | ||
- [ ] Previous test can cover this change. | ||
- [ ] No colde files have been changed. | ||
- [ ] Other reason <!-- Add your reason? --> | ||
|
||
- Behavior changed: | ||
|
||
- [ ] No. | ||
- [ ] Yes. <!-- Explain the behavior change --> | ||
|
||
- Does this need documentation? | ||
|
||
- [ ] No. | ||
- [ ] Yes. <!-- Add document PR link here. eg: https://github.com/apache/doris-website/pull/1214 --> | ||
|
||
- Release note | ||
|
||
<!-- bugfix, feat, behavior changed need a release note --> | ||
<!-- Add one line release note for this PR. --> | ||
None | ||
|
||
### Check List (For Reviewer who merge this PR) | ||
|
||
- [ ] Confirm the release note | ||
- [ ] Confirm test cases | ||
- [ ] Confirm document | ||
- [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into --> | ||
<!-- bugfix, feat, behavior changed need a release note --> | ||
<!-- Add a one-line release note for this PR. --> | ||
None | ||
|