Skip to content

Latest commit

 

History

History
44 lines (28 loc) · 2.23 KB

MAKEME.md

File metadata and controls

44 lines (28 loc) · 2.23 KB
Raw

Homework week 1:

Topics discussed in class this week:
• Git

Here you find the readings you have to complete before the second lecture.

Step 1: Share a useful resource

Deadline Monday

All share a video or a resource (this can be a drawing, an article or a podcast) that was helpful for you the last few weeks with learning JavaScript. Please share this in the channel of your class in Slack. Also write as small note about what the resource is about and why you think it's so helpful (you can share more than one if you like).

Step 2: Feedback

Deadline Monday

Give one of your fellow students feedback in Github about their homework of the previous week: Create an issue in their repo, telling them what they did great and what they can improve.

Step 3: Git homework

Deadline Wednesday

Git homework for this week:

Pair up with another student in your class. The homework requires two people to work together. Let's call them admin and user.

  1. admin creates a new repository on github called “animals” (without quotes).
  2. admin adds a file called “zoo.txt” with some animals generally found in a zoo.
  3. admin commits and pushes his changes (in master branch).
  4. admin adds user as a collaborator (find out how to add a collaborator to a git repository).
  5. user clones the repository from admin (find out how to clone a repository. Note that git init is not required when you clone a repository).
  6. user makes a new branch called user-dev.
  7. user adds another file called “pets.txt” with some animals generally found in a home.
  8. user commits and pushes his branch to remote.
  9. admin pulls the branch crated by user (find out how to pull changes from a repository).
  10. admin submits the link to his github repository (named "animals"), where Unmesh should be able to see the collaborator’s (i.e. user’s) branch along with his commits.

Note:

The user is not supposed to fork the admin’s repository. admin is supposed to add user as a collaborator and user should just clone the repository (i.e. user will only have the local copy of the repository). Only admin will have the github server copy of the repository. Of course, admin will have its local copy of the repository too.