A Git repository stores all project versions and history. It contains commits, branches, tags, and configuration files.

The .git folder holds metadata and object storage. Each commit references a snapshot of files and previous commits.

This structure enables fast branching and merging.

Branches allow developers to work on features independently.

Each branch points to a specific commit. Git creates lightweight branches without copying files.

Once work is complete, branches are merged back into the main branch. Branching supports parallel development and safer collaboration.

GitHub provides remote repositories for sharing code. Developers push changes and create pull requests.

Pull requests enable code review, discussion, and testing before merging. GitHub also tracks issues, commits, and contributors.

This makes team collaboration structured and transparent.

Git manages code history, while GitHub manages collaboration.

clone is for starting, pull is for syncing.

fetch is safer for reviewing changes before merging.

Private repos are preferred for company code.

Version control tracks changes in code over time. It allows rollback to previous versions. It helps teams collaborate without conflicts.

Git is the most popular version control system today. It improves code safety and productivity.

A commit is a snapshot of changes in the repository. Each commit has a unique hash ID.

Commits include message, author, and timestamp. They represent project history. Small, meaningful commits are best practice.

git status shows the current state of the working directory. It tells which files are modified, staged, or untracked.

It helps avoid accidental commits. Developers use it frequently before committing. It is one of the most used Git commands.

git add stages changes before committing. It moves files from working directory to staging area. Developers choose which changes to commit.

This gives control over commit content. Without git add, changes cannot be committed.

This command creates a commit with a message. The message describes the changes made.

Clear commit messages improve project history. Every commit should have a meaningful message. This is essential for team collaboration.

A branch is an independent line of development. It allows working on features without affecting main code.

Branches are cheap and fast. Most workflows use feature branches. Branching improves stability and productivity.

A merge conflict occurs when Git cannot automatically merge changes. It happens when the same file lines are modified.

Developers must manually resolve conflicts. Conflict resolution is a common interview topic. Proper branching reduces conflicts.

.gitignore tells Git which files to ignore. It prevents committing logs, secrets, or build files. It improves repository cleanliness.

Each project should include a .gitignore file. It enhances security and performance.

A remote repository is a version of the project hosted online. GitHub is the most common remote platform. Remotes allow team collaboration. Developers push and pull changes from remotes. It keeps everyone in sync.

git push uploads local commits to a remote repository. It shares changes with the team.

Pushing updates GitHub branches. Without push, changes stay local. Push is required for collaboration.

A pull request requests merging changes into another branch. It enables code review and discussion.

Teams review code before merging. Pull requests improve code quality. They are central to GitHub workflows.

GitHub enables collaboration, version control, and code hosting. It supports CI/CD, issue tracking, and reviews.

Recruiters often check GitHub profiles. It showcases developer skills. GitHub is essential in modern software development.