Hello! If you're at our workshop right now, please go here.

If you missed out on our workshop, but want to see what we did, view our slides here and the workshop here.

If you were at our workshop and/or are looking for some recap reading on Git & Github, go here.

Spotted a typo, a broken link, a garbled sentence, etc? We hear you're awesome at logging an issue ;)

Made by @alesssia, @estramcar & @feiphoon.

0. (Before the event) Sign up for your own Github account here: (https://github.com/join) & charge your laptop.
1. A welcome & brief introduction to basic Git concepts. (20min)
2. Everyone splits into groups of 2-4, one group per table. Say hello to your new teammates! (5min)

Here are today's steps to a good collaboration process, and the tasks for each one. Click on the titles to view the instructions.

3. Each group should pick one teammate to create a repository in Github. It should have a README, LICENSE, description and .gitignore.
4. The repository owner should add their teammates as collaborators on the repository.

5. Write your name in your group's repository README and commit it directly to master.

6. Create an issue based on a question (from a provided list).

7. Pick an issue to resolve, by assigning it to yourself and leaving a nice comment telling others you'll own it.
8. Create a branch to address your assigned issue.
9. Create a folder and file (with path instructions)
10. Commit your new file to your branch.

11. Use compare on your own branch to look at your own changes, and open a pull request. Link to the issue in the pull request description.
12. Catch-up point/timecheck (how many groups have at least one pull request open, 5min).

13. Look at the pull request you were assigned to review. View the file diff in the pull request to see what was changed.
14. Make a comment on any line in the file in the pull request (submit it with "Add a single comment").
15. Change to the pull request's branch and learn to find/navigate files.
16. Make a general comment on the pull request you are reviewing.
17. Approve the pull request.

18. Return to your pull request and read any comments left by others on yours. Click "Resolve conversation" on the comments (if everything is alright!)

19. Merge your own branch into master.

20. Delete your merged branch.
21. Close the issue that your pull request resolved.

🎉🎉🎉🎉🎉