friendica
/
friendica
mirror of https://github.com/friendica/friendica
6
0
Fork 1
Code Issues Packages Projects Releases 1 Wiki Activity

use typo.php to check before PR

This commit is contained in:
Tobias Diekershoff 2017-09-21 09:38:03 +02:00
parent ec95fb5c8d
commit 0d9e974122
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/Bugs-and-Issues.md
View File

@ -10,6 +10,7 @@ You can also contact the [friendica support forum](https://helpers.pyxis.uberspa
Bugs are rarely limited to one person, and the chances are somebody from another node has encountered the problem too, and will be able to help you. Bugs are rarely limited to one person, and the chances are somebody from another node has encountered the problem too, and will be able to help you.
If you're a technical user, or your site doesn't have a support page, you'll need to use the [Bug Tracker](https://github.com/friendica/friendica/issues). If you're a technical user, or your site doesn't have a support page, you'll need to use the [Bug Tracker](https://github.com/friendica/friendica/issues).
This is also used for issues with addons.
Please perform a search to see if there's already an open bug that matches yours before submitting anything. Please perform a search to see if there's already an open bug that matches yours before submitting anything.
Try to provide as much information as you can about the bug, including the **full** text of any error messages or notices, and any steps required to replicate the problem in as much detail as possible. Try to provide as much information as you can about the bug, including the **full** text of any error messages or notices, and any steps required to replicate the problem in as much detail as possible.
@ -17,4 +18,4 @@ It's generally better to provide too much information than not enough.
See [this article](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) to learn more about submitting **good** bug reports. The better your bug report, the more likely we are to be able to actually fix it. See [this article](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) to learn more about submitting **good** bug reports. The better your bug report, the more likely we are to be able to actually fix it.
And last but not least: It is better to report an issue you encountered even if you can't write the perfect bug report! And last but not least: It is better to report an issue you encountered even if you can't write the perfect bug report!