Detailed commit messages w/ Chris Toomey

1

Introduction

00:00 • 2min

2

Do We Really Need This?

01:55 • 2min

3

Git - Is That Really True?

04:19 • 2min

4

Git History Collapses Every So Many Times

06:38 • 2min

5

Is There a Value in Capturing History in Commits?

08:11 • 2min

6

Is It Worth the Effort to Produce This Lengthy Commit Message?

10:03 • 2min

7

Laravel

12:12 • 3min

8

The Seven Rules of a Great Get Commit Message

14:52 • 3min

9

The Third Most Important Rule of a Great Commit

17:50 • 3min

10

How to Write Good Get Commit Messages

20:32 • 2min

11

GitHub Markdown

22:21 • 2min

12

GitHub

24:30 • 4min

13

Are You Approaching Senior Developers?

28:56 • 4min

14

Commit Messages or Code Comments?

32:34 • 2min

15

Code Commit Messages

34:09 • 2min

16

The Importance of Committing Good Commit Messages

36:00 • 2min

17

Communication Is a Critical Skill for Software Developers

38:07 • 3min

18

Is It a Good Idea to Have a Developer?

40:48 • 2min

19

Is RTFM a Trope?

42:21 • 2min

20

The Next Generation of Commits Isn't Going to Work, but Is It?

44:09 • 2min

21

Commit Messages as a Best Practice

45:59 • 2min

22

Tests

47:49 • 5min