git_flashcards

(48 cards)

1
Q

Term

A

Definition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Version Control

A

System that tracks changes to files over time so you can recall specific versions later. Lets multiple people work on the same code without overwriting each other’s work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Git

A

Distributed version control system where every developer has full copy of repository. Most popular version control system used in software development.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Repository (Repo)

A

Folder that contains your project files and the entire history of changes. Can be local on your computer or remote on services like GitHub.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Commit

A

Snapshot of your project at a specific point in time. Includes a message describing what changed and why.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Branch

A

Separate line of development that lets you work on features without affecting main code. Allows multiple people to work on different features simultaneously.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Merge

A

Combines changes from one branch into another. Brings your feature work back into the main codebase.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Pull Request (PR)

A

Request to merge your changes into another branch. Allows team to review code before it gets merged.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Clone

A

Creates a local copy of a remote repository on your machine. Downloads entire project history and files.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Push

A

Uploads your local commits to a remote repository. Shares your work with others.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Pull

A

Downloads changes from remote repository and merges them into your local branch. Updates your code with other people’s work.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Fetch

A

Downloads changes from remote repository but doesn’t merge them. Lets you see what changed before deciding to merge.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Staging Area (Index)

A

Intermediate area where you prepare commits. Lets you choose which changes to include in next commit.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Working Directory

A

Folder on your computer where you make changes to files. Your actual project files you’re editing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Remote

A

Version of your repository hosted on the internet or network. Usually on GitHub, GitLab, or Bitbucket.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Origin

A

Default name for the remote repository you cloned from. Shorthand so you don’t have to type full URL every time.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

HEAD

A

Pointer to the current branch and commit you’re on. Tells git where you are in the project history.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Main (or Master)

A

Default primary branch where production-ready code lives. Used to be called master, now commonly called main.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Checkout

A

Switches between branches or restores files from history. Changes what code you’re looking at in working directory.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Stash

A

Temporarily saves uncommitted changes so you can work on something else. Useful when you need to switch branches but aren’t ready to commit.

21
Q

Merge Conflict

A

Happens when git can’t automatically combine changes from different branches. You have to manually decide which changes to keep.

22
Q

Rebase

A

Moves or combines commits from one branch onto another. Rewrites commit history to make it cleaner.

23
Q

Tag

A

Marks specific point in history as important. Usually used for release versions like v1.0 or v2.3.

24
Q

.gitignore

A

File that tells git which files or folders to ignore. Prevents accidentally committing sensitive data or build files.

25
Fork
Creates your own copy of someone else's repository. Lets you experiment without affecting original project.
26
git init
Initialize a new git repository in current folder.
27
git clone
Download a copy of remote repository to your local machine.
28
git status
Shows which files have changes and what's staged for commit.
29
git add
Adds files to staging area to prepare for commit. Use git add . to add all changed files.
30
git commit
Creates snapshot of staged changes with a message.
31
git push
Uploads local commits to remote repository.
32
git pull
Downloads and merges changes from remote repository.
33
git branch
Lists all branches or creates new branch.
34
git checkout
Switches to different branch or restores files.
35
git merge
Combines changes from one branch into current branch.
36
git log
Shows history of commits.
37
git diff
Shows differences between files or commits.
38
git stash
Temporarily saves uncommitted changes.
39
git reset
Undoes commits or unstages files.
40
git revert
Creates new commit that undoes previous commit.
41
GitHub
Git hosting platform with collaboration features.
42
GitLab
Git repository manager with CI/CD.
43
Bitbucket
Git repository hosting service from Atlassian.
44
Cherry-pick
Apply specific commit from one branch to another.
45
Release
Packaged version of software for distribution.
46
Semantic Versioning
Version numbering scheme (MAJOR.MINOR.PATCH).
47
Breaking Change
Change that breaks backward compatibility.
48
Backward Compatibility
New version works with old code/data.