The readings and responses listed here should take you approximately 35 minutes total.
To start this assignment:
- Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
- Click the Edit button when you're ready to start adding your answers.
- To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
Read David's article on Git and GitHub
- Use the article and outside resources (Google!) to describe the general process of a collaborative git workflow in the space below. When collaborating on a project, multiple people may want edit at simultaneously on different parts. Github tracks every change so that the group can see what works, what doesn't, and have a solid finished product. Each member of the group has the link to the master branch, which they can branch off as a clone, fork, or pull and make their own repository (directory of changes). These new branches are named descriptively for the goal of the edit. Once you've made a branch, all changes (insertions, deletions, etc.) are called commits, and each commit has a text field for the description and reason for the change. Members of the team can make commits, or edits, in their own branch, and push it back to Github where it can be reviewed before merging it on to the final branch.
- Watch this video. Then choose your own real-world class and objects of that class. In the space below, define and name the attributes and methods for your class and the associated objects.
class (blueprint)= dog objects (instances)= puppy, adult, senior attributes= color, size, breed methods= bark, wag, run, eat
@leighlars Nice work on your git workflow description!