liveBook · Manning

File tracking

As explained in Road to Kubernetes

File tracking is the recording of which files and file changes are included in successive version-control states.

File tracking records which files and changes belong to successive Git states. Saving a file is different from tracking it: git add prepares a saved state, while git commit finalizes it. section 2.3.3

Use the process to control which related changes enter a version-control state:

  • Run git add <path> to prepare selected files or folders at their current saved state. section 2.3.3
  • Use git reset <path> to unprepare a selected path before committing. section 2.3.3
  • Run git commit -m "message" to finalize changes since the previous commit. section 2.3.3
  • Track unrelated features separately so the resulting incremental changes remain understandable. section 2.3.3

How Road to Kubernetes covers it

How deep it goes
Explains saving, preparing, unpreparing, and committing, but stops short of broader version-control internals.
Examples
Uses Python and Node.js projects with git add commands for source files, dependencies, and lockfiles.
What it assumes
Assumes saved project files and a local repository while teaching beginners why saving and tracking differ.
What you can do after
Apply it via Git by selecting paths, revising selections, and committing coherent changes.
How it connects
Connects Git file tracking with commits, incremental changes, and separating unrelated features.
Cover of Road to Kubernetes
liveBookmanning.com
Read Road to Kubernetes on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of Road to Kubernetes. The section links point to the parts of the book it draws on.