From the course: Git for Teams
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Write descriptive commit messages - Git Tutorial
From the course: Git for Teams
Write descriptive commit messages
- [Instructor] In this lesson, we'll talk about the importance of writing a great commit message, and how they benefit your team. Well-crafted commit messages are the best way to communicate why the commit was necessary, giving some context to the code changes. Commit messages are also very handy when looking over recent changes to the code base. Commit messages can give you a quick idea of what has changed recently. Let's walk through a demonstration that will show you how to write a great commit message. When writing commit messages, developers often use the dash M flag to specify the commit message, using the command line. Unfortunately, this normally leads to a poor commit message. In fact, we've been doing it quite a bit throughout the course, but it's only for examples to save us some time. When working with a real code base, you need a better tool for the job. To write a great commit message, we should use a text editor instead of the command line. Let's walk through how to…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
(Locked)
Fundamentals of Git collaboration overview1m 43s
-
(Locked)
Common pitfalls: Untracked pulls4m 27s
-
(Locked)
Common pitfalls: Force push3m 16s
-
Best practices: Committing and syncing3m 29s
-
(Locked)
Best practices: gitignore4m 20s
-
(Locked)
Standardize line endings with autocrlf5m 20s
-
(Locked)
Branch naming1m 46s
-
(Locked)
Write descriptive commit messages6m 29s
-
(Locked)
Team composition and members roles5m 33s
-
(Locked)
-
-
-
-