Skip to content

Commit

Permalink
Prepare Issues and PRs for Prow
Browse files Browse the repository at this point in the history
  • Loading branch information
rmohr committed Jun 21, 2018
1 parent ba02741 commit e5ed5c5
Show file tree
Hide file tree
Showing 2 changed files with 42 additions and 14 deletions.
37 changes: 23 additions & 14 deletions .github/ISSUE_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1,21 +1,30 @@
<!--
Note that this is the issue tracker for Kubevirt.
<!-- This form is for bug reports and feature requests ONLY!
Also make sure that you visit our User Guide at https://kubevirt.io/user-guide/
-->

[provide a description of the issue]
**Is this a BUG REPORT or FEATURE REQUEST?**:

##### Version
[provide output of oc get deployment -o yaml -n kube-system | grep kubevirt]
> Uncomment only one, leave it on its own line:
>
> /kind bug
> /kind enhancement
##### Steps To Reproduce
1. [step 1]
2. [step 2]
3. [step 3]

##### Actual Result
**What happened**:

##### Expected Result
**What you expected to happen**:

##### Additional Information
[consider attaching the output of `$ oc get pod/vm/vmi -o json -n <namespace>` command to the issue]
[visit https://kubevirt.io/user-guide/]
**How to reproduce it (as minimally and precisely as possible)**:


**Anything else we need to know?**:

**Environment**:
- KubeVirt version (use `virtctl version`):
- Kubernetes version (use `kubectl version`):
- VM or VMI specifications:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g. `uname -a`):
- Install tools:
- Others:
19 changes: 19 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
<!-- Thanks for sending a pull request! Here are some tips for you:
1. Follow the instructions for writing a release note from k8s: https://git.k8s.io/community/contributors/guide/release-notes.md
-->

**What this PR does / why we need it**:

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #

**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. If no release note is required, just write "NONE".
-->
```release-note
```

0 comments on commit e5ed5c5

Please sign in to comment.