Track and resolve issues discovered in build processes within the Greysoft working envoronment.
During the course of working as part of the tech team, we encounter several issues, bugs and setbacks, most times we find promt solutions either with a simple google search or through a much rather complex debugging process, whichever is the case, when you eventually find the solution to your problem this repo would serve as a central error tracking solution seeing that the solution to you problems might also be applicable to some other person.
Where for any reason you were unable to find any solution to the problem, other individuals with a much broader scope of experience can step in to help.
Simply go to the issues tab and click on the New Issue button. When describing your issue, the folling should be taken into consideration:
- The platform, Library or Framwork you are working on should be indicated within parenthesis at the end of the title. *Example: * Unable to do a console.log() (Javascript)
- Make a step by step description of how your issue can be reproduced.
- Set up a git repo for your program if not already done so and include the link.
- Provide a Jsfiddle link to an existing implementation of your program (Optional).
- Make a step by step description of how the issue can be reported.
- Set up a git repo for your implementation if not already done so and include a link to it or create a pull request in the repo provided by the report.
- Provide a Jsfiddle link to an existing implementation of the resolved program unless working directly on the one provided by the report (Optional).
This repo was created for members of the Greysoft TECH Team but members of the public are also invited to share thier issues, solutions and experience.
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
The MIT License (MIT). Please see License File for more information.