-
Notifications
You must be signed in to change notification settings - Fork 78
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create PULL_REQUEST_TEMPLATE.md (#201)
- Loading branch information
Showing
1 changed file
with
62 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,62 @@ | ||
<!-- Thank you for contributing to KusionStack! | ||
Note: | ||
1. With pull requests: | ||
- Open your pull request against "main" | ||
- Your pull request should have no more than three commits, if not you should squash them. | ||
- It should pass all tests in the available continuous integration systems such as GitHub Actions. | ||
- You should add/modify tests to cover your proposed code changes. | ||
- If your pull request contains a new feature, please document it on the README. | ||
2. Please create an issue first to describe the problem. | ||
We recommend that link the issue with the PR in the following question. | ||
For more info, check https://kusionstack.io/docs/governance/contribute/ | ||
--> | ||
|
||
#### What type of PR is this? | ||
|
||
<!-- | ||
Add one of the following kinds: | ||
/kind bug | ||
/kind cleanup | ||
/kind documentation | ||
/kind feature | ||
--> | ||
|
||
#### What this PR does / why we need it: | ||
|
||
#### Which issue(s) this PR fixes: | ||
<!-- | ||
*Automatically closes linked issue when PR is merged. | ||
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. | ||
_If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_* | ||
--> | ||
Fixes # | ||
|
||
#### Special notes for your reviewer: | ||
|
||
#### Does this PR introduce a user-facing change? | ||
<!-- | ||
If no, just write "NONE" in the release-note block below. | ||
If yes, a release note is required: | ||
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required". | ||
--> | ||
```release-note | ||
``` | ||
|
||
#### Additional documentation e.g., design docs, usage docs, etc.: | ||
|
||
<!-- | ||
Please use the following format for linking documentation: | ||
- [Design]: <link> | ||
- [Usage]: <link> | ||
- [Other doc]: <link> | ||
--> | ||
```docs | ||
``` |