-
Notifications
You must be signed in to change notification settings - Fork 72
Error Reporting
Alex Kuchta edited this page Jan 25, 2017
·
6 revisions
- Create an Issue in GitHub: Speaking as a developer, this is definitely the preferred option. Check out the Issues page and see if somebody else is having the same problem. If yes, leave a comment to help move us along. If not, create a new issue so we know what is happening - be as detailed as possible!
- Note: It is very important to provide as much detail as possible when reporting a bug - please follow the issue tracker template carefully and make sure you answer all of the required fields!
- Check Out Gitter: GitHub's official IM solution, Gitter provides you with instant access to a real life person (probably Alex). This is a great way to get in touch with the developer as well as other users in the community - go straight to the Vulnerator Gitter Room to get started
- Email the Developers: Please, please, please use this as a last resort or if you feel your issue is too sensitive to air in the open. To find our email addresses, click the "About" link in the title bar of the application, then select the appropriate link from the newly opened flyout
If you come across something, please let us know - we can't catch everything in testing (thought we certainly try!), and your input is the most valuable asset we have. Above all else, thank you for being patient and working with us!
Finished with the Wiki? Be sure to check out some of the other features within the Vulnerator GitHub page: