Git

Git stores snapshots linked through a commit graph. A working tree contains editable files, the index selects changes for the next commit and references name positions in history. Branches are movable references rather than separate complete copies of a project. Merging combines histories; rebasing rewrites a sequence onto a different base. These operations differ in how they preserve identity and ancestry. Git itself is distinct from GitHub, which hosts repositories and adds review and automation. Version control records changes but does not judge whether a change is correct.

A practitioner inspects status and diffs before recording work, groups related changes into coherent commits and writes messages explaining their purpose. They compare branches, review conflicts semantically and use history to investigate regressions. They manage ignored files and avoid treating large datasets or secrets as ordinary source. When collaborating, they choose history operations that respect shared work. The useful result is a patch and history that reviewers can understand and maintainers can use to reproduce or reverse a particular change.

A successful merge can contain semantic conflicts, while rewriting shared history can disrupt others' references. Committing a file does not preserve external data, environments or hosted model versions automatically. Reverting code may also require corresponding data or infrastructure changes. Inspect the final tree and operation scope before reset, rebase or cleanup. Git proficiency includes understanding what has been recorded and what remains outside the repository.