Skip to content

Commit 563e92b

Browse files
committed
Update template
1 parent 3453319 commit 563e92b

1 file changed

Lines changed: 17 additions & 91 deletions

File tree

.github/ISSUE_TEMPLATE.md

Lines changed: 17 additions & 91 deletions
Original file line numberDiff line numberDiff line change
@@ -1,100 +1,26 @@
1-
<!--
1+
✖ USAGE QUESTIONS → Use these dedicated resources:
2+
Docs - http://www.semantic-ui.com
3+
Chat - https://gitter.im/Semantic-Org/Semantic-UI
4+
SO - https://stackoverflow.com/questions/tagged/semantic-ui?sort=votes
25

3-
✖ Please do not post usage questions to GitHub Issues.
4-
For these types of questions use our Gitter chatroom or StackOverflow.
56

6-
7-
✔ Submitting Bugs and Enhancements.
8-
Before submitting a bug make sure you do the following:
9-
10-
- Check out our contributing guide for info on our release cycle.
11-
12-
- Fork our boilerplate JSFiddle to create a test case for your bug.
13-
If a bug is apparent in the docs, that's ok as a test case, just
14-
make it clear exactly how to reproduce the issue. Only bugs that
15-
include a test case can be triaged.
16-
17-
18-
✔ Pull Requests
19-
When adding pull requests, be sure to merge into the next branch.
20-
If you need to demonstrate a fix in next release, you can use our
21-
JSFiddle.
22-
23-
24-
25-
If your bug uses a third party framework like Ember, Meteor, or Angular.
26-
Be sure to submit the issue to their respective issues boards. If you
27-
are confident the bug is part of the 'vanilla' SUI release, keep in mind
28-
not all maintainers are familiar with all framework and a simple test
29-
case is greatly appreciated.
30-
31-
32-
33-
Gitter: https://gitter.im/Semantic-Org/Semantic-UI
34-
StackOverflow: https://stackoverflow.com/questions/tagged/semantic-ui
35-
Contributing Guide: https://github.com/Semantic-Org/Semantic-UI/blob/master/CONTRIBUTING.md
36-
JSFiddle boilerplate: https://jsfiddle.net/ca0rovs3/
37-
38-
39-
40-
Make sure you name your issue correctly!
41-
42-
Semantic UI boards use a special naming convention to help tag issue titles by the component
43-
the issue is related to.
7+
✔ BUGS → This form is required:
8+
✔ Enhancements → Only specific enhancements with detailed descriptions.
449

45-
Bugs
46-
Please tag titles in the format "[Component] Sub-type should do correct behavior". Please use
47-
standard title case for titles, including the bracketed tag.
10+
### Issue Titles
11+
Use the format: [Component] Component Should Do X
4812

49-
For example
50-
[Dropdown] Multiple Selection Should Preserve "Set Selected" Order
51-
[Validation] - E-mail Validation Should Handle Cyrillic
52-
[Button] - Grouped Buttons Should Display Correctly on Mobile
53-
54-
55-
Enhancements
56-
For new feature requests, you can use the format "[Component] Add new feature"
13+
For example: [Checkbox] onChange Should Fire when update triggered via DOM
5714

58-
For example
59-
[Dropdown] Add "Clearable" Setting
60-
[Validation] Add Rules for Zipcode Validation
61-
[API] Add "onProgress" callback setting
62-
63-
-->
15+
### Steps
6416

17+
### Expected Result
6518

19+
### Actual Result
6620

67-
# Bug Report Template
21+
### Version
22+
x.y.z
6823

69-
## Description
70-
Describe the bug you are having
71-
72-
## How to reproduce
73-
A step by step guide on how to reproduce the bug
74-
75-
## Expected behavior
76-
The result which you where expecting
77-
78-
## Resulting behavior
79-
The actual result
80-
81-
## Environment Information
82-
- Operating System (OS version)
83-
- Browser (Browser version)
84-
85-
## Link to JSFiddle
86-
Link to the JSFiddle which recreates the bug
87-
88-
89-
90-
91-
# Feature Request Template
92-
93-
## Description
94-
Describe the feature and why the feature should be added
95-
96-
## Implementation
97-
Tell us how you would implement the feature
98-
99-
## Example
100-
If you can show an example of the feature using an image or links
24+
### Testcase
25+
[Fork, update, and replace to show the bug]:
26+
https://jsfiddle.net/ca0rovs3/

0 commit comments

Comments
 (0)