Skip to content

Commit 58326a4

Browse files
authored
Merge pull request #359 from vkucera/git
Git: Add more references to tutorials and commit message advice
2 parents 7b7e865 + 7812011 commit 58326a4

1 file changed

Lines changed: 17 additions & 7 deletions

File tree

docs/gettingstarted/gitbasics.md

Lines changed: 17 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,19 @@ title: Git basics
55

66
# Git basics
77

8-
Git is a version control system, or VCS, tracks the history of changes as people and teams collaborate on projects together.
8+
[Git](https://git-scm.com/) is a [version control system (VCS)](https://en.wikipedia.org/wiki/Version_control) that tracks the history of changes as people and teams collaborate on projects together.
99
As developers make changes to the project, any earlier version of the project can be recovered at any time.
1010

11-
Developers can review project history to find out:
12-
13-
- Which changes were made?
14-
- Who made the changes?
15-
- When were the changes made?
16-
- Why were changes needed?
11+
Developers can review project history to find out _who_ made _what_ changes _when_ and _why_.
1712

1813
## Complete tutorials
1914

15+
### [Git Documentation](https://git-scm.com/docs)
16+
17+
- [Git Book](https://git-scm.com/book/en/v2)
18+
- [Git: gittutorial](https://git-scm.com/docs/gittutorial)
19+
- [Git: giteveryday](https://git-scm.com/docs/giteveryday)
20+
2021
### [Atlassian Git Tutorial](https://www.atlassian.com/git/tutorials)
2122

2223
Selected sections:
@@ -41,8 +42,17 @@ Selected sections:
4142
- [Resolving merge conflicts after a Git rebase](https://docs.github.com/en/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase)
4243
- [Resolving a merge conflict using the command line](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)
4344

45+
## How to write a Git commit message
46+
47+
- [Chris Beams: How to Write a Git Commit Message](https://cbea.ms/git-commit/)
48+
- [Tim Pope: A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
49+
- [Peter Hutterer: On commit messages](https://who-t.blogspot.com/2009/12/on-commit-messages.html)
50+
- [Git Book: Commit Guidelines](https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_commit_guidelines)
51+
- [Python for Data Science: Git best practices](https://www.python4data.science/en/latest/productive/git/best-practices.html#write-meaningful-commit-messages)
52+
4453
## Cheat sheets
4554

55+
- [Git Cheat Sheet](https://git-scm.com/cheat-sheet)
4656
- [GitHub Git Cheat Sheet - GitHub Cheatsheets](https://training.github.com/downloads/github-git-cheat-sheet/)
4757
- [Git cheat sheet \| Atlassian Git Tutorial](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet)
4858
- [git - the simple guide](https://rogerdudler.github.io/git-guide/)

0 commit comments

Comments
 (0)