@@ -8,8 +8,8 @@ the developers managing and developing for free this open source project during
8
8
Thank you for this, and in return we will reciprocate that respect in addressing your issue
9
9
or assessing patches with goodwill.
10
10
11
- Using the issue tracker = search before
12
- ---------------------------------------
11
+ Search before
12
+ -------------
13
13
14
14
The issue tracker is the preferred channel for bug reports, features requests and submitting pull
15
15
requests, but please respect the following restrictions:
@@ -18,18 +18,18 @@ requests, but please respect the following restrictions:
18
18
[ Stack Overflow] ( http://stackoverflow.com ) instead.
19
19
* Please, please, please, ** SEARCH** before you file a new issue or request.
20
20
21
- Using the issue tracker = read before
22
- -------------------------------------
21
+ Guidelines
22
+ ----------
23
23
24
24
Before using the issue tracker, we require you read the specific guidelines, depending on the topic:
25
25
a bug report, a feature request or a pull request.
26
26
27
- ### Bug report
27
+ ### Bug Report
28
28
29
29
Good bug reports are extremely helpful - thank you! Good bug reports are also quite rare.
30
- To help and raise the bug report quality, you must read the wiki document about [ Bug Reports] ( https://github.com/YOURLS/YOURLS/wiki/Bug-Report )
30
+ To help and raise the bug report quality, ** you _ must _ read the wiki document about [ Bug Reports] ( https://github.com/YOURLS/YOURLS/wiki/Bug-Report ) . **
31
31
32
- ### Feature request
32
+ ### Feature Request
33
33
34
34
Feature requests are welcome. But take a moment to find out whether your idea fits the scope and
35
35
goals of the project. Check also the [ Roadmap] ( https://github.com/YOURLS/YOURLS/wiki/Road-Map ) ,
@@ -39,10 +39,9 @@ It's up to you to make a strong case to convince the project's developers of the
39
39
Please provide as much detail and context as possible and get in touch. Feel free to detail how you envision
40
40
things, be they about (pseudo)code, interface, mockup, etc...
41
41
42
- ### Pull request
42
+ ### Pull Request
43
43
44
44
Good pull requests are a fantastic help. But please get in touch before you start working,
45
45
it's always a sad moment to dismiss a patch for which a coder has spent a lot of time because
46
46
it simply does not fit the project. Please read the wiki
47
- document about [ Pull requests] ( https://github.com/YOURLS/YOURLS/wiki/Pull-Request )
48
-
47
+ document about [ Pull requests] ( https://github.com/YOURLS/YOURLS/wiki/Pull-Request ) .
0 commit comments