As a part-time computer science teacher, I often give workshops to learn about computers and their tools.
Several times I met teams that had been using Git and Github for many years but were having a lot of trouble.
The basis was known but in practice.
"Wait, stay still, I'll do that and you can get it back."
"I'm stuck working on the same file."
"Pass me your file, I'll add it to my PR."
I'm pretty sure you've heard that before!
It may sound funny but it's quite symptomatic of a lack of practice and reflexes to have when you get to use Git.
Very often users know how to manage but do rather obscure things.
Often users know how to manage but do rather obscure things.
A former colleague preferred to do several cherry-pick to retrieve the work of one of his colleagues' successive commits rather than use a rebase.
What if I designed a workshop that would allow teams to learn the right reflexes together when using Git and Github?
I had the opportunity to participate in several Coding Dojo/Kata programming sessions and I wanted to be inspired by this model.
Instead of working on code, the workshop I designed focuses on git and its use.
Here is the link to the workshop, available free of charge on Github.
Slashgear
/
git-kata
When you know the bases of git but sometimes you have problemes with it. This "code kata" could help you to deal with git problems
Git Kata, learn how to use git in team
When you know the bases of git but sometimes you have problemes with it. This "code kata" could help you to deal with git problems
| Duration | 2h30 |
|---|---|
| Supplies needed | - (optional) Story Cubes - video projector - internet |
| Max participant | Team of 4, max 12 people |
| Required skills | The objective of this workshop is to sharpen the use of git in teams in order to limit the everyday problems that can be encountered with Git (interdependence, conflicts,...) |
If you are a kata participant, follow these instructions
- One of the Dev team member should create an empty repository and share the url to the other members
- Make sure each participant have the possibility to commit and merge commit on this repository
- The repository should be empty
If you are the the workshop facilitator
SPOIL SPOIL Click here, don't spoil yourself if
It's all in the README.
Leave me your opinions and feedback in comments.
Top comments (5)
What is that Git GUI you have in the hero image? It looks nice.
+1 for this. What VS plugins??
Thanks @antoine ! Be careful of your typo in the project description "problemes" => "problems"
Looks like GitKraken. :)
Gitkraken it is. But I really prefer Webstorm vps feature.