This is a git flow based project

We're not using the full weight of true `git flow` but we are using a light version of it.

The **number one** rule of `git flow` is:

> Master branch should be production ready at all times

This. means you will not be allowed to make a pull request against master.

The secondary rule of git flow is:
> You may not break the `development` branch.

If your code causes a crash, it will not be accepted.

## So, how do I `git flow` then?
It's actually pretty easy.
1. `$ git clone git@github.com:CodingRainbow/asteroids-advanced.git`
2. `$ cd asteroids-advanced`
3. `$ git checkout -b feature/name-of-your-feature`
4. Work in your feature branch until you're done.
5. Stage your working files and commit them with a short message
6. Push your changes up to the repo
7. Create a new pull request against `development`
8. @shiffman, myself, and/or another member of the organization will look over it, and either accept it, or reject it with helpful criticism as to how to get it accepted.
9. Lather. Rinse. Repeat.

# ONE LAST THING:
To make sure you've ready this, please comment with your favorite coding related gif below. If there's no comment from you, then your pull will not be accepted.

### now
###     it's time
###                     to

Der Issue nennt keine Dokumentationsdatei, keinen Test und keinen Einstiegspunkt. Beginne damit, die Hinweise des Repositorys zu Beiträgen oder Branches zu finden und sie mit den Git Flow-Anweisungen hier zu vergleichen. Für den Abschluss wäre eine klar identifizierte Dokumentationsänderung erforderlich, aber dieser Issue gibt keine an.

Vom Indexierungsmodell aus dem Issue-Text verfasst.