Skip to content

Commit c1a2550

Browse files
committed
* added some repo ground rules
1 parent bc93092 commit c1a2550

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Repo.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ Reporting an issue on GitHub
44
====================================
55

66
------------------------------------
7-
<a href=whattoreport></a>
7+
<a href="whattoreport"></a>
88
#### What to report?
99

1010
Be sure you are reporting either 1) a bug you have discovered or 2) a feature request.
@@ -13,7 +13,7 @@ People have been abusing the GitHub issues system for a while to ask all kind of
1313

1414
Long story short - make sure you are reporting something and not just asking how this or that is done.
1515

16-
<a href=howtoreport></a>
16+
<a href="howtoreport"></a>
1717
#### How to report a problem/request a feature?
1818

1919
Describe what you expected to happen and what actually happened instead.
@@ -24,7 +24,7 @@ I need to be able to **reproduce the problem** in order to fix it.
2424

2525
Of course the best would be if you already have fixed the problem yourself, then create a pull request. If you do - before you send a pull request run ALL TEST CASES on both IOS and OSX! Add a test case for what you have fixed, since it obviously haven’t been covered with one if there was a problem to be fixed.
2626

27-
<a href=helpwithcode></a>
27+
<a href="helpwithcode"></a>
2828
#### In case you need help with your code/models …
2929

3030
In case you **do need help** with your code: your best start is to **read the repo README**, many people don’t and it really is the best place to find many answers.

0 commit comments

Comments
 (0)