Skip to content

Latest commit

 

History

History
33 lines (23 loc) · 1.81 KB

CONTRIBUTING.md

File metadata and controls

33 lines (23 loc) · 1.81 KB
Raw

Creating Issues

  • 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).

Contributing

Coding style

  1. Always use tabs.
  2. Always place braces on new lines.
  3. Use C# 6 whenever possible.
  4. Follow the standard MS C# naming conventions (short version). Also see: How to name things in programming
  5. Know when to make exceptions.

Commits and Pull Requests

Keep the commit log as healthy as the code. It is one of the first places new contributors will look at the project.

  1. No more than one change per commit. There should be no changes in a commit which are unrelated to its message.
  2. Follow these conventions when writing the commit message.

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

Need help?

You can always ask for help on Gitter or the HearthSim IRC channel, #Hearthsim on Freenode.