See also Get Involved on the main website.
-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
Before submitting, please read the Style Guide to know more about coding conventions and benchmarks.
- Open an issue to start a discussion (or join Gitter or IRC). It's best to talk these things through before spending a lot of time writing code.
- Ask any question about the code base on Gitter or IRC (#futhark on Freenode). Please don't open GitHub issues just to ask questions.