@@ -9,11 +9,11 @@ community looks forward to your contributions. 🎉
99
1010## Table of Contents
1111
12- - [ Code of Conduct] ( #code-of-conduct )
13- - [ I Have a Question] ( #i-have-a-question )
14- - [ I Want To Contribute] ( #i-want-to-contribute )
15- - [ Reporting Bugs] ( #reporting-bugs )
16- - [ Suggesting Enhancements] ( #suggesting-enhancements )
12+ - [ Code of Conduct] ( #code-of-conduct )
13+ - [ I Have a Question] ( #i-have-a-question )
14+ - [ I Want To Contribute] ( #i-want-to-contribute )
15+ - [ Reporting Bugs] ( #reporting-bugs )
16+ - [ Suggesting Enhancements] ( #suggesting-enhancements )
1717
1818## Code of Conduct
1919
@@ -29,8 +29,8 @@ in this issue.
2929
3030If you then still feel the need to ask a question and need clarification, we recommend the following:
3131
32- - Open an [ Issue] ( ../../issues/new ) .
33- - Provide as much context as you can about what you're running into.
32+ - Open an [ Issue] ( ../../issues/new ) .
33+ - Provide as much context as you can about what you're running into.
3434
3535We will then take care of the issue as soon as possible.
3636
@@ -49,11 +49,11 @@ A good bug report shouldn't leave others needing to chase you up for more inform
4949investigate carefully, collect information and describe the issue in detail in your report. Please complete the
5050following steps in advance to help us fix any potential bug as fast as possible.
5151
52- - Make sure that you are using the latest version.
53- - To see if other users have experienced (and potentially already solved) the same issue you are having, check if there
54- is not already a bug report existing for your bug or error in the [ bug tracker] ( ../..//issues?q=label%3Abug ) .
55- - Collect information about the bug
56- - Possibly your input and the output
52+ - Make sure that you are using the latest version.
53+ - To see if other users have experienced (and potentially already solved) the same issue you are having, check if there
54+ is not already a bug report existing for your bug or error in the [ bug tracker] ( ../..//issues?q=label%3Abug ) .
55+ - Collect information about the bug
56+ - Possibly your input and the output
5757
5858#### How Do I Submit a Good Bug Report?
5959
@@ -62,21 +62,21 @@ following steps in advance to help us fix any potential bug as fast as possible.
6262
6363We use GitHub issues to track bugs and errors. If you run into an issue with the project:
6464
65- - Open an [ Issue] ( ../../issues/new ) . (Since we can't be sure at this point whether it
66- is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
67- - Explain the behavior you would expect and the actual behavior.
68- - Please provide as much context as possible and describe the _ reproduction steps_ that someone else can follow to
69- recreate the issue on their own. This usually includes your code.
70- - Provide the information you collected in the previous section.
65+ - Open an [ Issue] ( ../../issues/new ) . (Since we can't be sure at this point whether it
66+ is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
67+ - Explain the behavior you would expect and the actual behavior.
68+ - Please provide as much context as possible and describe the _ reproduction steps_ that someone else can follow to
69+ recreate the issue on their own. This usually includes your code.
70+ - Provide the information you collected in the previous section.
7171
7272Once it's filed:
7373
74- - The project team will label the issue accordingly.
75- - A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no
76- obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as ` needs-repro ` . Bugs with
77- the ` needs-repro ` tag will not be addressed until they are reproduced.
78- - If the team is able to reproduce the issue, it will be marked ` needs-fix ` , as well as possibly other tags (such as
79- ` critical ` ), and the issue will be left to be implemented by someone.
74+ - The project team will label the issue accordingly.
75+ - A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no
76+ obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as ` needs-repro ` . Bugs with
77+ the ` needs-repro ` tag will not be addressed until they are reproduced.
78+ - If the team is able to reproduce the issue, it will be marked ` needs-fix ` , as well as possibly other tags (such as
79+ ` critical ` ), and the issue will be left to be implemented by someone.
8080
8181### Suggesting Enhancements
8282
@@ -86,22 +86,22 @@ community to understand your suggestion and find related suggestions.
8686
8787#### Before Submitting an Enhancement
8888
89- - Make sure that you are using the latest version.
90- - Perform a [ search] ( ../../issues ) to see if the enhancement has already been
91- suggested. If it has, add a comment to the existing issue instead of opening a new one.
92- - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to
93- convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful
94- to the majority of our users and not just a small subset.
89+ - Make sure that you are using the latest version.
90+ - Perform a [ search] ( ../../issues ) to see if the enhancement has already been
91+ suggested. If it has, add a comment to the existing issue instead of opening a new one.
92+ - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to
93+ convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful
94+ to the majority of our users and not just a small subset.
9595
9696#### How Do I Submit a Good Enhancement Suggestion?
9797
9898Enhancement suggestions are tracked as [ GitHub issues] ( ../../issues ) .
9999
100- - Use a ** clear and descriptive title** for the issue to identify the suggestion.
101- - ** Describe the current behavior** and ** explain which behavior you expected to see instead** and why. At this point
102- you can also tell which alternatives do not work for you.
103- - You may want to ** include screenshots and animated GIFs** which help you demonstrate the steps or point out the part
104- which the suggestion is related to. You can use [ this tool] ( https://www.cockos.com/licecap/ ) to record GIFs on MacOS and
105- Windows, and [ this tool] ( https://github.com/colinkeenan/silentcast ) or [ this tool] ( https://github.com/GNOME/byzanz ) on Linux.
106- - ** Explain why this enhancement would be useful** for the community. You may also want to point out the
107- other projects that solved it better and which could serve as inspiration.
100+ - Use a ** clear and descriptive title** for the issue to identify the suggestion.
101+ - ** Describe the current behavior** and ** explain which behavior you expected to see instead** and why. At this point
102+ you can also tell which alternatives do not work for you.
103+ - You may want to ** include screenshots and animated GIFs** which help you demonstrate the steps or point out the part
104+ which the suggestion is related to. You can use [ this tool] ( https://www.cockos.com/licecap/ ) to record GIFs on MacOS and
105+ Windows, and [ this tool] ( https://github.com/colinkeenan/silentcast ) or [ this tool] ( https://github.com/GNOME/byzanz ) on Linux.
106+ - ** Explain why this enhancement would be useful** for the community. You may also want to point out the
107+ other projects that solved it better and which could serve as inspiration.
0 commit comments