This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 124
Bug reporting
Evan edited this page Apr 27, 2016
·
4 revisions
####"There is a bug in your code! What do I do?"
-
Github issues are an effective way to keep track of bugs and features that we need to add.
To report a bug start by: Searching for existing issue reports. No one wants to deal with duplicate reports.
-
No duplicates found? Good, now make your issue report by clicking here.
When making your report, be sure to mention:
- Title: Start with
[Bug]
- Title: Short description of what the issue is. (Clearer the better.)
- Your browser. (Firefox, Google Chrome, etc.)
- What version of the bot you are using. (Can be found at the top of the bot's code in Tamper/Greasemonkey.)
- What you think caused this issue. (On your end, you don't need to diagnose our code, tell us what you did that caused it.)
- If you can, suggest a solution. (Again, you don't need to be technical in your description.)
- Title: Start with
-
Pat yourself on the back for being a productive contributor of an open source project.
#Slither.io Bot ##Suggested Reading:
##For Contributors: