cerc-io/solidity
16
0
Fork 0
mirror of https://github.com/ethereum/solidity synced 2023-10-03 13:03:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #12412 from ethereum/labels-in-issue-templates

Browse Source 
Labels in issue templates
This commit is contained in:
Kamil Śliwak 2021-12-16 17:40:41 +01:00 committed by GitHub
commit 76e83a9b05
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 15 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/ISSUE_TEMPLATE/bug_report.md vendored
View File

@ -1,6 +1,7 @@
---
name: Bug Report
about: Bug reports about the Solidity Compiler.
labels: ["bug :bug:"]
---
<!--## Prerequisites
@ -8,13 +9,12 @@ about: Bug reports about the Solidity Compiler.
- First, many thanks for taking part in the community. We really appreciate that.
- 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.
- Support questions are better asked in one of the following locations:
- [Solidity chat](https://gitter.im/ethereum/solidity)
- [Stack Overflow](https://ethereum.stackexchange.com/)
- [Solidity chat](https://gitter.im/ethereum/solidity)
- [Stack Overflow](https://ethereum.stackexchange.com/)
- Ensure the issue isn't already reported.
- 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.
*Delete the above section and the instructions in the sections below before submitting*
-->
## Description

13
.github/ISSUE_TEMPLATE/documentation_issue.md vendored
View File

@ -1,22 +1,17 @@
---
name: Documentation Issue
about: Solidity documentation.
labels: ["documentation :book:"]
---
## Page
<!--
Please link directly to the page which you think has a problem
-->
<!--Please link directly to the page which you think has a problem.-->
## Abstract
<!--
Please describe in detail what is wrong.
-->
<!--Please describe in detail what is wrong.-->
## Pull request
<!--
Please link to your pull request which resolves this issue
-->
<!--Please link to your pull request which resolves this issue.-->

26
.github/ISSUE_TEMPLATE/feature_request.md vendored
View File

@ -1,6 +1,7 @@
---
name: Feature Request
about: Solidity language or infrastructure feature requests.
labels: ["feature"]
---
<!--## Prerequisites
@ -8,40 +9,29 @@ about: Solidity language or infrastructure feature requests.
- First, many thanks for taking part in the community. We really appreciate that.
- 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.
- Support questions are better asked in one of the following locations:
- [Solidity chat](https://gitter.im/ethereum/solidity)
- [Stack Overflow](https://ethereum.stackexchange.com/)
- [Solidity chat](https://gitter.im/ethereum/solidity)
- [Stack Overflow](https://ethereum.stackexchange.com/)
- Ensure the issue isn't already reported (check `feature` and `language design` labels).
*Delete the above section and the instructions in the sections below before submitting*
-->
## Abstract
<!--
Please describe by example what problem you see in the current Solidity language
and reason about it.
-->
<!--Please describe by example what problem you see in the current Solidity language and reason about it.-->
## Motivation
<!--
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.
-->
<!--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.-->
## Specification
<!--
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.
-->
<!--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.-->
## Backwards Compatibility
<!--
All language changes that introduce backwards incompatibilities must include a section describing
these incompatibilities and their severity.
All language changes that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity.
Please describe how you propose to deal with these incompatibilities.
-->
-->