We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
fix(sidebar): missing link for git-message This fix also introduce a few other links to the official reference and book.
doc(quick-start): Branches & PRs Tutorial explaining the [feature-branch] workflow with detailed objectives and the complete set of CLI commands and their corresponding results on the local git status, log and on github. This tutorial quickly explain how to rebase a branch to solve a conflict on github. It does not explain in-depth the various merge techniques that are merge/squash+cherry-pick/rebase+fast-forward and simply blindly alwlays use merge on github.
doc(commit-message): in-depth explanation This article contains an in-depth explanation of what commit messages are, their origine, where they are used and how one can improve them. It is very common for students to overlook their git history and commit message. They don't do in-depth reviews, rarely discover their mate's work thanks to the `git log` and absolutely never `git blame` files. It is important they learn that it is not always possible to reach someone to ask questions about a bit of code (during a review or later while maintening a software) and that it is better if they can learn to be autonomous early. This complete article explain all that thanks to the enphasis on commit messages. May they not leave school knowing how to write clear commit messages, at least they'll leave school knowing it "is something" and that is is important "at least in some companies".
doc(commit-message): origine & structure This is an early draft of a new "explanation"-type document about commit messages. For now it explains the origine and structure (only title and trailers for now) of commit messages. Future additions will contains bits about where those messages are used (review/historic/blame) to give a better understanding of what should be inside them.
doc(collab): cli steps
doc(quick-start): why is my hash different?
fix(quick-start): typo
doc(install): config default pull strategy In cas no default pull strategy is configured, the first time one `git pull` with no extra argument, the operation is abort and the user is prompt to configure the default strategy. Use the `merge` strategy for now as it was the default strategy in previous git versions.
doc(quick-start): add/commit/push desktop steps
doc(quick-start): add/commit/push cli steps Also include an empty part-2 so that links are not broken
doc(install-linux-mac): Git Credential Manager
chore(*): soft word-wrap
doc(quick-start): intro & github steps
doc(install): git install steps for windows
doc(install): use separators in windows tuto
doc(install): fix broken links
chore(wiki): handy draft notes for future pages
doc(install): git install steps for windows (wip)
doc(install): git install steps for POSIX systems
doc(install): github account creation steps
chore(wiki): Initial commit