Revision control

## Contributor guidelines
We'd love for you to contribute to this repository. Before you start, we'd like you to take a look and follow these guidelines:
- [Submitting an Issue](#submitting-an-issue)
- [Creating a pull request](#creating-a-pull-request)
- [Coding Rules](#coding-rules)
- [Swift style](#swift-style)
- [Whitespace](#whitespace)
- [Commits](#commits)
### Submitting an Issue
If you find a bug in the source code or a mistake in the documentation, you can help us by submitting an issue to our repository. Before you submit your issue, search open and closed issues, maybe your question was already answered.
### Creating a pull request
* All pull requests must be associated with a specific Issue. If an issue doesn't exist please first create it.
* Before you submit your pull request, search the repository for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
* For commiting in your Pull Request, You can checkout [Commits](#commits) for more.
### Coding Rules
#### Swift style
* Swift code should generally follow the conventions listed at
* Exception: we use 4-space indentation instead of 2.
* This is a loose standard. We do our best to follow this style
#### Whitespace
* New code should not contain any trailing whitespace.
* We recommend enabling both the "Automatically trim trailing whitespace" and "Including whitespace-only lines" preferences in Xcode (under Text Editing).
* <code>git rebase --whitespace=fix</code> can also be used to remove whitespace from your commits before issuing a pull request.
### Commits
* Each commit should have a single clear purpose. If a commit contains multiple unrelated changes, those changes should be split into separate commits.
* If a commit requires another commit to build properly, those commits should be squashed.
* Follow-up commits for any review comments should be squashed. Do not include "Fixed PR comments", merge commits, or other "temporary" commits in pull requests.