This workshop will take you through the basics and a little more on how to use Git and GitHub. Tighten your sitbelts to enjoying some time-travel analogy to understand how Git works, how you can connect it to GitHub and how this will help you with your version control. Git is a free and open source distributed version-control system designed to maintain code, track changes, recover old versions and collaborate with other developers.
Alexander Botxki
Bruna Piereck
James Collier
Tuur Muyldermans
If you don’t have experience with command line it is essential that you follow a quick course since this skills are very important to be able to use git and GitHub.
To not get lost during the course start the crash course Introduction to Linux command line on VIB e-learnign system.
For this course we are going to use some tools, some are mandatory some are sugestions that we believe can possibly make your experience better and the didatics more simple. You can find the detailes instructions for any operating system* in our Get Ready chapter.
Summary of what you might need:
- WSL with GitBash (for windowns users)
- Git installed in your terminal (MAC & Linux)
- MarkText (Editor Sugestion - MarkDown)
- Ungit (Visualization tool - NOT mandatory)
Day 1
| Time | Session |
|---|---|
| 9h30 | Configurations & Introduction |
| 11h00 | Coffee break |
| 11h15 | Routine usage part 1 (status-stage-commit) |
| 13h00 | Lunch |
| 14h00 | History & Comparing Versions |
| 14h40 | Coffee break |
| 14h55 | From Git to GitHub |
| 17h00 | End of the day |
Day 2
| Time | Session |
|---|---|
| 9h30 | Collaborating in GitHub |
| 11h00 | Coffee break |
| 11h15 | Experimenting Risk Free: Working with Branchs |
| 13h00 | Lunch |
| 14h00 | Solving Conflicts and changing old versions |
| 14h40 | Coffee break |
| 14h55 | Tagging & Forking |
| 17h00 | End of the day |
-
Enumerate the primary purpose and advantages of Git in version control. [Knowledge]
-
Identify and name the difference between Git and GitHub. [Knowledge]
-
Explain the differences between branches and forks and their use cases. [Knowledge]
-
Describe and Distinguish between the development area, staging area, local and remote repositories. [Knowledge and Comprehension]
-
Explain the importance of commit messages and their role in tracking changes. [Comprehension]
-
Discuss the significance of staging changes before committing it. [Comprehension]
-
Apply the key steps in Git routine, including staging, committing changes to update the working tree. [Application]
-
Illustrate the purpose and use of branches in Git for testing new features and collaborations. [Comprehension and Application]
-
Use the Git commands to share changes from local to remote repository and vice versa. [Application]
-
Create a new repository on GitHub, clone it locally, make edits, and push changes back to GitHub. [Application]
-
Be able to clone a GitHub repository locally and perform edits. [Application]
-
Evaluate the impact of well-crafted
commitmessages on project documentation and collaboration. [Analysis] -
Analyse the benefits and challenges of using branches in Git for project development. [Analysis]
-
To use commands to check the status and unique ID's of content modificaitons. [Application]
Check some chapters with complementary reading. You will review what you saw in the course and get some extra tips and information, such as using Rstudio on GitHub.