Skip to content

Commit

Permalink
chore(github): update issue/pr templates
Browse files Browse the repository at this point in the history
  • Loading branch information
Sean Hamilton committed Dec 23, 2019
1 parent d285f16 commit c40be8d
Show file tree
Hide file tree
Showing 4 changed files with 119 additions and 32 deletions.
44 changes: 33 additions & 11 deletions .github/ISSUE_TEMPLATE/Bug_report.md
Original file line number Diff line number Diff line change
@@ -1,30 +1,52 @@
---
name: 🐛 Bug Report
about: When something isn't working correctly
labels: ":mag_right: needs investigating"
name: ":bug: Bug Report"
about: "Use this if something isn't working how you think it should or you think you've found a bug"
labels: "type/bug", "state/awaiting-investigation", "state/awaiting-triage"
---

# Bug Report

<!--
Title Format
[Scope] Summary of what is broken
Please use the following issue title format:
"[<scope>] <summary of what is wrong>"
-->

# Bug Report
<!-- Describe what's wrong in great detail (required). -->

## Steps to reproduce
<!-- Tell us how to reproduce your issue (required). -->
1.
2.
3.

## Expected result
<!-- Tell us what result you were expecting (required). -->

## Actual result
<!-- Tell us what the actual result was (required). -->

## Testcase
<!-- Fork https://jsfiddle.net/31d6y7mn -->
<!--
If possible create an example of your issue via a JSFiddle.
How to create an example:
1. Open the following JSFiddle - https://jsfiddle.net/31d6y7mn
2. Click "Fork" at the top
3. Add the minimum required HTML, CSS and JavaScript which reproduces
your issue
4. Click "Save" at the top
5. Copy the URL of your fiddle and link it here
-->

## Screenshot (if possible)
<!--
If possible include images or gifs of your issue.
## Screenshot (when possible)
![]()
E.g. Incorrect component CSS should include an image of what the
component looks like.
If your looking for a tool we recommend ShareX - https://github.com/ShareX/ShareX
-->

## Version
x.x.x
<!-- Include the version of the library you are using (required). -->
2.x.x
45 changes: 35 additions & 10 deletions .github/ISSUE_TEMPLATE/Feature_request.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,43 @@
---
name: 🚀 Feature Request
about: Suggest a new feature
labels: ":zap: enhancement"
name: ":rocket: Feature Request"
about: "Use this to suggest new feature/enhancements"
labels: "type/feat", "state/awaiting-triage"
---

<!--
Please use the following issue title format:
"[<scope>] <summary of your request>"
-->

# Feature Request
<!--
Explain your request in great detail (required).
Things to consider:
- Why should we add this feature/enhancement
- What problem(s) does it solve
- Complexity
- How we should implement it
-->

## Description
Explain what you want in great detail
## Example (if possible)
<!--
If possible demonstrate your request via a JSFiddle.
## Example
How to create an example:
1. Open the following JSFiddle - https://jsfiddle.net/31d6y7mn
2. Click "Fork" at the top
3. Add the HTML, CSS and JavaScript which shows your request
4. Click "Save" at the top
5. Copy the URL of your fiddle and link it here
-->

## Testcase (when possible)
<!-- Fork https://jsfiddle.net/31d6y7mn -->
## Screenshot (if possible)
<!--
If possible include images or gifs of your request.
## Screenshot (when possible)
![]()
E.g. new component request should include images of the component
in other frameworks and on websites.
If your looking for a tool we recommend ShareX - https://github.com/ShareX/ShareX
-->
22 changes: 17 additions & 5 deletions .github/ISSUE_TEMPLATE/Help_wanted.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,22 @@
---
name: 📓 Support Question
about: If you have a question or need a helping hand
labels: ":thought_balloon: usage question"
name: ":notebook: Support Question"
about: "Use this if you have a any question or need a helping hand"
labels: "type/usage", "state/awaiting-triage"
---

# Help Wanted
<!-- Tell us your question or what you need help with. (required) -->

## Problem
Describe your problem in great detail
## Testcase
<!--
If your asking for help please include an example of your problem to help
us provide the best support.
How to create an example:
1. Open the following JSFiddle - https://jsfiddle.net/31d6y7mn
2. Click "Fork" at the top
3. Add the minimum required HTML, CSS and JavaScript which reproduces
your problem
4. Click "Save" at the top
5. Copy the URL of your fiddle and link it here
-->
40 changes: 34 additions & 6 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,43 @@
<!--
Please read the contibuting guide before you submit a pull request
https://github.com/fomantic/Fomantic-UI/blob/master/CONTRIBUTING.md
Please read our Contributing Guide and Code of Conduct before you
submit a pull request.
Contributing Guide: https://github.com/fomantic/Fomantic-UI/blob/master/CONTRIBUTING.md
Code of Conduct: https://github.com/fomantic/Fomantic-UI/blob/master/CODE_OF_CONDUCT.md
----
Please use the following pull request title format:
"[<scope>] <summary of what you fixed/changed>"
-->

## Description
<!-- Describe what you fixed/changed in great detail (required). -->

## Testcase
<!-- Fork https://jsfiddle.net/31d6y7mn -->
<!--
If possible create an example of your change via a JSFiddle.
How to create an example:
1. Open the following JSFiddle - https://jsfiddle.net/31d6y7mn
2. Click "Fork" at the top
3. Add the minimum required HTML, CSS and JavaScript which shows your change
4. Click "Save" at the top
5. Copy the URL of your fiddle and link it here
-->

## Screenshot (when possible)
![]()
## Screenshot (if possible)
<!--
If possible include images or gifs of your issue.
E.g. Incorrect component CSS should include an image of what the
component looks like.
If your looking for a tool we recommend ShareX - https://github.com/ShareX/ShareX
-->

## Closes
#222 #333 #444
<!--
List all the issues this pull request closes (only if it does).
-->
#<issue id>, #<issue id>, #<issue id>

0 comments on commit c40be8d

Please sign in to comment.