### Pull requests

Good pull requests - patches, improvements, new features - are a fantastic help.

If you've spotted any small, obvious errors and want to help out by patching it, that will be much appreciated.

If your contribution involves a significant amount of work or substantial changes to any part of the project, please open a "contribution enquiry" issue first to check that the work is wanted or matches the goals of the project.

All pull requests should remain focused in scope and avoid containing unrelated commits.

Please follow this process; it's the best way to get your work merged into the project:

1. Fork the project.
1. Clone your fork ( git clone git@github.com:<your-username>/<repo-name>git).
1. Add an upstream remote (git remote add upstream git://github.com/<upsteam-owner>/<repo-name>.git).
1. Get the latest changes from upstream (e.g. git pull upstream <dev-branch>).
1. Create a new topic branch to contain your feature, change, or fix ( git checkout -b <topic-branch-name> ).
1. Make sure that your changes adhere to the current coding conventions used throughout the project - indentation, accurate comments, etc.
1. Commit your changes in logical chunks. Please adhere to these git commit message guidelines or your pull request is unlikely be merged into the main project.
1. Push the branch up to your fork ( git push origin <topic-branch-name> ).
1. Open a Pull Request with a clear title and description. Please mention which browsers you tested in.

If you have any other questions about contributing, please feel free to contact me.