Skip to content

Commit 76e83a9

Browse files
authored
Merge pull request #12412 from ethereum/labels-in-issue-templates
Labels in issue templates
2 parents e497803 + 9e0f03b commit 76e83a9

File tree

3 files changed

+15
-30
lines changed

3 files changed

+15
-30
lines changed

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
---
22
name: Bug Report
33
about: Bug reports about the Solidity Compiler.
4+
labels: ["bug :bug:"]
45
---
56

67
<!--## Prerequisites
78
89
- First, many thanks for taking part in the community. We really appreciate that.
910
- We realize there is a lot of information requested here. We ask only that you do your best to provide as much information as possible so we can better help you.
1011
- Support questions are better asked in one of the following locations:
11-
- [Solidity chat](https://gitter.im/ethereum/solidity)
12-
- [Stack Overflow](https://ethereum.stackexchange.com/)
12+
- [Solidity chat](https://gitter.im/ethereum/solidity)
13+
- [Stack Overflow](https://ethereum.stackexchange.com/)
1314
- Ensure the issue isn't already reported.
1415
- The issue should be reproducible with the latest solidity version; however, this isn't a hard requirement and being reproducible with an older version is sufficient.
1516
1617
*Delete the above section and the instructions in the sections below before submitting*
17-
1818
-->
1919

2020
## Description
Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,17 @@
11
---
22
name: Documentation Issue
33
about: Solidity documentation.
4+
labels: ["documentation :book:"]
45
---
56

67
## Page
78

8-
<!--
9-
Please link directly to the page which you think has a problem
10-
-->
9+
<!--Please link directly to the page which you think has a problem.-->
1110

1211
## Abstract
1312

14-
<!--
15-
Please describe in detail what is wrong.
16-
-->
13+
<!--Please describe in detail what is wrong.-->
1714

1815
## Pull request
1916

20-
<!--
21-
Please link to your pull request which resolves this issue
22-
-->
17+
<!--Please link to your pull request which resolves this issue.-->
Lines changed: 8 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,47 +1,37 @@
11
---
22
name: Feature Request
33
about: Solidity language or infrastructure feature requests.
4+
labels: ["feature"]
45
---
56

67
<!--## Prerequisites
78
89
- First, many thanks for taking part in the community. We really appreciate that.
910
- We realize there is a lot of data requested here. We ask only that you do your best to provide as much information as possible so we can better help you.
1011
- Support questions are better asked in one of the following locations:
11-
- [Solidity chat](https://gitter.im/ethereum/solidity)
12-
- [Stack Overflow](https://ethereum.stackexchange.com/)
12+
- [Solidity chat](https://gitter.im/ethereum/solidity)
13+
- [Stack Overflow](https://ethereum.stackexchange.com/)
1314
- Ensure the issue isn't already reported (check `feature` and `language design` labels).
1415
1516
*Delete the above section and the instructions in the sections below before submitting*
16-
1717
-->
1818

1919
## Abstract
2020

21-
<!--
22-
Please describe by example what problem you see in the current Solidity language
23-
and reason about it.
24-
-->
21+
<!--Please describe by example what problem you see in the current Solidity language and reason about it.-->
2522

2623
## Motivation
2724

28-
<!--
29-
In this section you describe how you propose to address the problem you described earlier,
30-
including by giving one or more exemplary source code snippets for demonstration.
31-
-->
25+
<!--In this section you describe how you propose to address the problem you described earlier, including by giving one or more exemplary source code snippets for demonstration.-->
3226

3327
## Specification
3428

35-
<!--
36-
The technical specification should describe the syntax and semantics of any new feature. The
37-
specification should be detailed enough to allow any developer to implement the functionality.
38-
-->
29+
<!--The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow any developer to implement the functionality.-->
3930

4031
## Backwards Compatibility
4132

4233
<!--
43-
All language changes that introduce backwards incompatibilities must include a section describing
44-
these incompatibilities and their severity.
34+
All language changes that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity.
4535
4636
Please describe how you propose to deal with these incompatibilities.
47-
-->
37+
-->

0 commit comments

Comments
 (0)