-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Similar to other kubevirt projects they include the release_note field at the PR making easier to modify it. Signed-off-by: Or Shoval <[email protected]>
- Loading branch information
Showing
1 changed file
with
28 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,28 @@ | ||
<!-- Thanks for sending a pull request! | ||
Before you click the 'Create pull request' make sure that: | ||
- This PR introduces a single feature of fix, just one | ||
- This PR does not leave the main branch broken | ||
- Every commit in this PR has a commit message explaining what do you change, | ||
why and what is the outcome | ||
- If your change introduces a complex concept or a change to user interaction | ||
with the project or the application, make sure to document it | ||
If you don't comply with these rules, you waste your energy, time of reviewers | ||
and cause suffering of future generations. | ||
--> | ||
|
||
**What this PR does / why we need it**: | ||
|
||
**Special notes for your reviewer**: | ||
|
||
**Release note**: | ||
<!-- Write your release note: | ||
1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". | ||
2. Follow the instructions for writing a release note from k8s: https://git.k8s.io/community/contributors/guide/release-notes.md | ||
3. If no release note is required, just write "NONE". | ||
--> | ||
|
||
```release-note | ||
``` |