INTERNAL OF GIT : HOW GIT WORKS ? || PART 2 : GIT OBJECTS (HINDI)

Описание: Git's internals revolve around three main objects: trees, blobs, and commits. These objects are fundamental to Git's version control system.

Blob (Binary Large Object):

A blob is simply a file. It stores the content of a file but does not contain any metadata about the file, such as its name or permissions.
Blobs are uniquely identified by the SHA-1 hash of their content, which ensures that identical files are stored only once.
Fun Fact: Despite being called "binary large object," blobs can store any type of file content, including text files. They are called "binary" because they can handle any type of data, not just text.
Tree:

A tree object represents a directory. It contains references to blobs (files) and other tree objects (subdirectories) along with metadata such as filenames and file permissions.
Trees are also identified by their SHA-1 hashes, which depend on the content of the directory and the content of its children (blobs and other trees).
Fun Fact: Git stores file names in trees as a combination of the file's mode (permissions), type (blob or tree), and name. This allows Git to track changes to file permissions and directory structures effectively.
Commit:

A commit object represents a snapshot of the repository at a specific point in time. It includes a reference to a tree object (representing the state of the directory at that time) and metadata such as the commit author, commit message, and parent commits (for tracking history).
Commits are also identified by SHA-1 hashes, which depend on the content of the commit (the tree it references), the commit message, and other metadata.
Fun Fact: Git's commit history forms a directed acyclic graph (DAG), where each commit points to its parent(s). This graph structure enables efficient branching and merging operations.
Fun Fact:

Git's object model is designed to be content-addressable. This means that objects are identified by the content they store rather than by their location or name. It allows Git to ensure data integrity and prevent duplication efficiently.
The SHA-1 hashing algorithm, used to generate unique identifiers for Git objects, was once considered secure but is now considered vulnerable to collision attacks. However, Git's usage of SHA-1 for object IDs is still effective for its purposes.
Git's internal data model is surprisingly simple, consisting primarily of these three types of objects, yet it enables powerful version control capabilities, including branching, merging, and distributed workflows.

#git #github #javascript #coding #java #python #programming #code #webdevelopment #linux #programmer #php #devops #training #webdev