guidelines for contributing Hearthstone-Deck-Tracker

https://github.com/Epix37/Hearthstone-Deck-Tracker/blob/master/CONTRIBUTING.md

 

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.