-
Notifications
You must be signed in to change notification settings - Fork 4
Github Workflow
◄ Back (Syllabus) Next (The Setup) ►
First, make sure you're up on git. Refer to Jae's excellent tutorial and the accompanying recitation if you need somewhere to get started. Github also has some excellent getting started tutorials: https://help.github.com/articles/set-up-git/
Then, make sure you understand the Github Flow. You're going to need it for your team project.
Then take a look at this:
Git Commit Message Conventions. All commits must follow the conventional-changelog commit conventions. I promise doing so will be worth your while. (You don't have to do this for the first homework). You may also use build in addition to the other 7 allowed types to refer to plugins, tools, dotfiles, configuration, etc. that contribute to a project's infrastructure, tooling, or setup, but that is not a feature of the project itself. Google uses the word chore for this, but I feel that chore seems to refer more to a maintenance task, and doesn't quite give tooling and DevOps stuff the credit it deserves.
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.