Skip to content

Commit

Permalink
Merge pull request #199 from cucumber/update-pr-templates
Browse files Browse the repository at this point in the history
Update PR and issue templates to match Cucumber JVM repo
  • Loading branch information
danascheider committed Jun 9, 2020
2 parents cba063a + fa8924e commit 547314c
Show file tree
Hide file tree
Showing 4 changed files with 62 additions and 84 deletions.
48 changes: 0 additions & 48 deletions .github/ISSUE_TEMPLATE.md

This file was deleted.

36 changes: 36 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,36 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: Bug
assignees: ''

---

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

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

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

**Context & Motivation**

How has this issue affected you? What are you trying to accomplish? Providing context helps us come up with a solution that is most useful in the real world.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Your Environment**
- Versions used [e.g 4.0.0]
- Operating System and version [e.g. * Operating System and version:]
- Build tool (if applicable)

**Additional context**
Add any other context about the problem here
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: Feature Request
assignees: ''

---

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
42 changes: 6 additions & 36 deletions .github/PULL_REQUEST_TEMPLATE.md
@@ -1,39 +1,9 @@
<!-- These sections are meant as guidance for you. If something doesn't fit, you can just skip it. -->
**Is your pull request related to a problem? Please describe.**

## Summary
A link to an issue or a clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

<!--- Provide a general summary description of your changes -->
**Describe the solution you have implemented**
A clear and concise description of what happens.

## Details

<!--- Describe your changes in detail -->

## Motivation and Context

<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## How Has This Been Tested?

<!--- Please add tests for changes to the code, otherwise we probably won't merge it -->

<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, tests ran to see how -->
<!--- your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] I've added tests for my code
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
**Additional context**
Add any other context or screenshots about the pull request here.

0 comments on commit 547314c

Please sign in to comment.