- Have a look at the FAQ.
- Check if a similar issue already exists (use the search function).
- In case of a bug/crash/problem: Add as much detail as possible, including crash reports/logs (see here).
- Always use tabs.
- Use LF line endings.
- Always place braces on new lines.
- Use C# 6 whenever possible.
- Follow the standard MS C# naming conventions (short version). Also see: How to name things in programming
- Know when to make exceptions.
Keep the commit log as healthy as the code. It is one of the first places new contributors will look at the project.
- No more than one change per commit. There should be no changes in a commit which are unrelated to its message.
- Follow these conventions when writing the commit message.
- Keep the diffs as clean as possible. Avoid unnecessary line changes.
When filing a Pull Request, make sure it is rebased on top of most recent master. If you need to modify it or amend it in some way, you should always appropriately fixup the issues in git and force-push your changes to your fork.
Also see: Github Help: Using Pull Requests
Want to help translate the app? Take a look at the HDT-Localization repository.
You can always ask for help on Gitter or the HearthSim IRC channel, #Hearthsim
on Freenode.