lesnitsky/git-tutor has 382 GitHub stars and 8 forks. Star changes are not measured yet. Last checked 2026-11-13 17:05 UTC. Last push 2023-01-05.
計測したスター増加
- 24時間
- 履歴を収集中
- 7日間
- 履歴を収集中
- 15日間
- 履歴を収集中
- 1か月
- 履歴を収集中
期間ごとの純増数です。期間は重複しており、日別の値ではありません。未計測の値は空欄です。スター数は注目度の指標であり、品質の保証ではありません。
概要
:octocat:+md=:heart: Awesome tutorials from your git log
学習README.md
オリジナルGit Tutor

Generate step-by-step markdown tutorials from your git history
Motivation
There is tons of tutorials on medium, personal blogs etc. Writing detailed and complete guide how to build things is kinda hard and people are lazy, so those tutorials sometimes incomplete, code examples don't work as-is (some "prerequisite" step was not included in tutorial), sometimes it walks you through only some pieces of code and you can find the rest in repo. But you have no idea how the rest works.
Git is a perfect tool to build smth incrementally (commits). git-tutor walks through commit history and generates markdown, placing commit message first, content of a commit afterwards. Write markdown to your commit messages – have a nice tutorial later with single command
Example tutorials
Some rules
- keep commits small and explain almost every line of code you're writing
- write markdown to your commit messages
- don't skip anything. Simple copy-paste should work to reproduce the result of your tutorial
- writing code is fun. Explaining how code works is even more of fun
Installation
npm i -g nodegit
npm i -g git-tutor
Usage
git-tutor . > README.md
Tips and tricks
I don't like commiting every line of code. What should I do to keep tutorial clean?
That's fine, I don't like it either. You can use git add -p and split your work into smaller chunks later
Git treats # as a comment by default
To be able to use this symbol and add headings you should reconfigure git cleanup symbol
git config commit.cleanup whitespace
What if I want to leave general comment/explanation without any code
Git allows commits without any content
git commit --allow-empty
How to use my favorite editor for writing markdown
Writing a lot of markdown is not really convenient in default git editor like vi, I prefer doing it in vscode as it allows to preview parsed markdown with all styling applied. To use vscode as git editor
- Install
codecommand in$PATH(Shift + CMD + P => Search forPATH) git config core.editor "code --wait"
Default commit message template contains status in comment, how to remove it
You can pass --no-status flag to a commit command, this will strip those commented lines
git commit --no-status
You can also use your custom commit template:
- create empty file and place it somwhere in your file system (e.g.
~/.gitmsg) git config commit.template ~/.gitmsg
Unsolved issues
- i18n (cherry-pick to new locale branch with translation?)
- updates to previous commits (rebase works, but not convenient)
- collobaration
LICENSE
関連プロジェクトを探す
sindresorhus/awesome
😎 あらゆる興味深いトピックに関する Awesome リスト [注意: 既存のプルリクエストに追いつけるまで、プルリクエストは一時的に無効になっています]
536,352 スターEbookFoundation/free-programming-books
:books: 無料で入手できるプログラミングの書籍
401,545 スターnilbuild/developer-roadmap
開発者のキャリア成長を支える、インタラクティブなロードマップ、ガイド、その他の教育コンテンツ。
371,953 スターvinta/awesome-python
「Python で X をしたい。どのツールを使えばいい?」に答える決定版リスト。
334,508 スター