Howdy! Thanks for being interested enough in improving this dumb tool that you’re reading instructions for how to do so. Here are some general guidelines to make sure your code is up to our (very lax) standards.
- All PRs should be made to the
staginbranch. Yes, that spelling is correct. Sean typed it in wrong when we first started the project, but we decided to just keep it this way, because we're assholes. - Make sure your PRs pass Codacy’s tests. (This will be very easy because Codacy can’t parse D.)
- Don’t worry too much about coding or documentation style. Most functions should have Javadoc-style descriptions, but if it’s obvious, don’t worry about it. This will become more specific if it needs to.
- Reference issues in PRs. If there isn’t a relevant issue, it would be super cool if you opened one!
- If there’s a task manager that you (and preferably several other people) use, and you’d like to use it in
aight, submit an issue with thenew-providertag. For bonus points, describe its API/format/general technical details. - Horse. (:horse:.)