What Is a Git Commit? A Saved Point in Your Website Code History

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

1. 1

   Step 1: A commit records file changes

   0:18

   It can include changes across one or several files.

   On-screen labels: One or more files; Recorded changes; Project history.

2. 2

   Step 2: A message describes the change

   0:30

   A useful message helps others understand what was done.

   On-screen labels: Brief description; Useful context; Reason for the update.

3. 3

   Step 3: Each commit has an identifier

   0:42

   A hash gives the saved change a specific reference.

   On-screen labels: Commit hash; Exact reference; Identifiable change.

4. 4

   Step 4: History records authorship

   0:54

   The record helps show who made a change and when.

   On-screen labels: Recorded author; Change time; Project timeline.

5. 5

   Step 5: A commit is not a release promise

   1:06

   Saving a change does not prove that the live site now uses it.

   On-screen labels: Saved project change; Deployment status; Live version check.

6. 6

   Step 6: Reference it during support

   1:18

   An exact change reference can help a maintainer investigate.

   On-screen labels: Relevant commit; Affected files; Observed website result.

Common questions

Go further