WEBVTT

00:00:00.000 --> 00:00:06.000
What does a developer mean by committing a change?

00:00:06.000 --> 00:00:13.000
A commit records a set of file changes in the project history.

00:00:13.000 --> 00:00:18.000
Understand the saved change record.
6 commit basics.

00:00:18.000 --> 00:00:30.000
A commit records file changes
It can include changes across one or several files.
One or more files · Recorded changes · Project history

00:00:30.000 --> 00:00:42.000
A message describes the change
A useful message helps others understand what was done.
Brief description · Useful context · Reason for the update

00:00:42.000 --> 00:00:54.000
Each commit has an identifier
A hash gives the saved change a specific reference.
Commit hash · Exact reference · Identifiable change

00:00:54.000 --> 00:01:06.000
History records authorship
The record helps show who made a change and when.
Recorded author · Change time · Project timeline

00:01:06.000 --> 00:01:18.000
A commit is not a release promise
Saving a change does not prove that the live site now uses it.
Saved project change · Deployment status · Live version check

00:01:18.000 --> 00:01:30.000
Reference it during support
An exact change reference can help a maintainer investigate.
Relevant commit · Affected files · Observed website result

00:01:30.000 --> 00:01:39.000
Your checklist
A commit records file changes · A message describes the change · Each commit has an identifier · History records authorship · A commit is not a release promise · Reference it during support

00:01:39.000 --> 00:01:47.000
Use a clear reference when discussing a code change.
jerseyweb.je