Github

Question 1

Git

Answer 1

A distributed version control system used to track changes in source code during software development

Question 2

Repository (Repo)

Answer 2

A collection of files and folders along with the entire history of changes

Question 3

GitHub

Answer 3

A web-based platform for version control and collaboration

Question 4

Clone

Answer 4

To copy a repository from a remote server (like GitHub) to your local machine

Question 5

Fork

Answer 5

Creating a personal copy of someone else’s project in GitHub. Forks allow you to freely experiment with changes

Question 6

Branch

Answer 6

A parallel version of a repository used to work on different features or fixes without affecting the main code base

Question 7

Commit

Answer 7

A snapshot of changes made to a repository. Commits are used to save changes to the local repository

Question 8

Push

Answer 8

Sending committed changes to a remote repository (like GitHub)

Question 9

Pull

Answer 9

Fetching and merging changes from a remote repository to your local repository

Question 10

Pull requests (PR)

Answer 10

A proposed change submitted by a user in a fork of a repository. Notifies the original project maintainers for review and potential merge

Question 11

Merge

Answer 11

Combining changes from one branch to another

Question 12

Conflict

Answer 12

A situation that occurs when Git is unable to automatically merge changes in different branches, requiring manual intervention

Question 13

Remote

Answer 13

A repository hosted on a server, like GitHub, rather than on your local machine

Question 14

Origin

Answer 14

The default name for the remote repository on GitHub from which you cloned your local repository

Question 15

Upstream

Answer 15

The original repository that you forked on GitHub. Often used in to keep your fork synced with the upstream repository

Question 16

.gitignore

Answer 16

A file specifying intentionally untracked files and directories that Git should ignore