Github Workflow

First, make sure you're up on git.

Git Commit Message Conventions. All commits must follow the conventional-changelog commit conventions. ###### I promise doing so will be worth your while.

For more information about these conventions and there motivation, see the AngularJS Git Commit Message Conventions: https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit

We'll also be following, to a large extent, the Angular team's contributing guidelines in the team projects. https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md

Further, we will use this repo's issues for asking and answering questions collaboratively. This is not because I consider this to be a better way to handle this than a forum. It's actually not really what issues are designed for, but Github's markdown support for code is excellent and I want to make sure you get used to using issues as your primary means of communicating on projects. Using issues for questions about JavaScript and collaborating on Github directly when there is no repo to worry about will make it that much easier when it is time to use issues to collaborate on your repos.