Skill · Git · Collaborate with Git
Standardize a team's commit messages and have them checked automatically
Write commit messages in the Conventional Commits format (type, scope, breaking change), have non-compliant ones rejected by a commit-msg hook and by a CI job on every merge or pull request, and map each type to the SemVer version increment it triggers.
- 1 lesson
- ~35 min of reading
- 1 quiz
- 0 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · 1 prerequisite
Recommended before · 1
This skill, for you
Standardize a team's commit messages and have them checked automatically
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
1 lesson, about ~35 min, in program order. Each lesson ends with its quiz.
The program
1 lesson · ~35 min
- 1Conventional Commits (in French)· 35 min
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
1 quiz
At the end of the lessons: passed at 70%, it confirms the skill.
Practice
No guided lab
No guided lab practices it yet.
Proof
No proof
Neither a challenge nor a mission with a proof yet.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
Taught by
Same block · Collaborate with Git