Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update issue templates #105

Merged
merged 1 commit into from
Jan 31, 2019
Merged

Update issue templates #105

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
---
name: Bug report
about: Create a report to help us improve
title: "[BUG]"
labels: kind/bug
assignees: ''

---

**Describe the bug:**
A clear and concise description of what the bug is.

**Expected behaviour:**
A clear and concise description of what you expected to happen.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shall we have a "Current behaviour" section to let the issue-creator tell us exactly what problem they are experiencing, as opposed to what they expected to happen..?

Copy link
Contributor Author

@swapnilgm swapnilgm Jan 30, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First section i.e. Describe the bug is exactly where issue raiser will right the current behaviour. And i don't think, we need to rename the section. @georgekuruvillak WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Current behaviour is ambiguous. Describe the bug seems better to me.

**How To Reproduce (as minimally and precisely as possible):**

**Logs:**

**Screenshots (if applicable):**


**Environment (please complete the following information):**
- Etcd version/commit ID :
- Etcd-backup-restore version/commit ID:
- Cloud Provider [All/AWS/GCS/ABS/Swift]:

**Anything else we need to know?**:
14 changes: 14 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
name: Feature request
about: Suggest an improvement for this project
title: "[Feature]"
labels: kind/enhancement
assignees: ''

---

**Feature (What you would like to be added):**

**Motivation (Why is this needed?):**

**Approach/Hint to the implement solution (optional):**