Version Control Systems 101 Flashcards

(61 cards)

1
Q

A Version Control System that stores all changes in a database on a single computer

A

Local Version Control Systems (LVCS)

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

A Version Control System that stores all changes on a remote server, allowing multiple users to collaborate

A

Centralized Version Control Systems (CVCS)

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

A Version Control System that has no single main server. Every user has a full copy of the project including its history

A

Distributed Version Control Systems (DVCS)

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

This VCS has an advantage: Simple and Fast

A

Local VCS

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

This VCS has an advantage: Team Collaboration and Project Tracking

A

Centralized VCS

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

This VCS has an advantage: No single failure point, fast, and supports offline work.

A

Distributed VCS

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

This VCS has a disadvantage: No collaboration and High Data Loss Risk

A

Local VCS

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

This VCS has a disadvantage: Requires network and also has Server Failure Risks

A

Centralized VCS

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

This VCS has a disadvantage: Slightly Complex Setup

A

Distributed VCS

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

The Best Use Case for this VCS is: Personal Projects

A

Local VCS

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

The Best Use Case for this VCS is: Small to medium teams

A

Centralized VCS

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

The Best Use Case for this VCS is: Large projects and open-source development

A

Distributed VCS

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

This was created in 2005 by Linus Torvalds after BitKeeper SCM stopped offering a free version

A

Git

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

One Git’s Key Features which means every user has a full copy of the repository

A

Distributed

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

One Git’s Key Features which means it uses snapshots instead of tracking differences, making switching between versions quick

A

Fast

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

This creates independent copies of the project for testing features.

A

Branching

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

This combines changes back into the main project when ready.

A

Merging

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

This temporarily saves work to switch tasks without losing progress.

A

Stashing

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

This uses checksums to detect changes and prevent corruption

A

Checksum-Based Tracking

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

One of the Three States System that is the current version being edited.

A

Working Directory

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

One of the Three States System that files are prepared for commit.

A

Staging Area

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

One of the Three States System where committed changes are stored

A

Git Directory

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

The process of Git which is to get a copy of the project.

A

Clone the Repository

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

The process of Git which is to view pas changes.

A

Check Project History

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
The process of Git which is to avoid modifying the main project directly.
Create and Switch to a New Branch
26
The process of Git which is to prepare changes for commit
Modify Files and Add to Staging
27
The process of Git which is to save work locally with a description.
Commit Changes
28
The process of Git which is after approval, joins the changes to the main project.
Merge Back to Main Project
29
The process of Git which makes your work visible to others
Push Changes to Remote Server
30
The First Process of Git
Clone the Repository
31
The Second Process of Git
Check Project History
32
The Third Process of Git
Create and Switch to a New Branch
33
The Fourth Process of Git
Modify Files and Add to Staging
34
The Fifth Process of Git
Commit Changes
35
The Sixth Process of Git
Merge Back to Main Project
36
The Last Process of Git
Push Changes to Remote Repository
37
A platform that stores software projects, allowing multiple developers to collaborate.
Project Hosting Service
38
Enables tracking of team progress and access to code from any device.
Project Hosting Service
39
There is one central repository and the developers can commit only to that repo.
Centralized Development
40
The repositories are interconnected and can be edited and worked on by several developers simultaneously.
Distributed Development
41
It is a platform for version control and collaboration, built on top of Git.
GitHub
42
It is a widely used VCS that manages versioned projects efficiently, combining, tracking, teamwork, and change history in one system.
Git
43
(Git vs GitHub) It is a distributed version control system that tracks code changes.
Git
44
(Git vs GitHub) It is a Git-based project hosting service.
GitHub
45
(Git vs GitHub) It works locally and in the cloud.
Git
46
(Git vs GitHub) It provides a user-friendly interface for Git
GitHub
47
(Git vs GitHub) It allows branching, merging, and collaboration
Git
48
(Git vs GitHub) It includes features like pull requests, issue tracking, and team collaboration.
GitHub
49
(Git vs GitHub) Not Tied to a specific platform---other services use Git as well.
Git
50
(Git vs GitHub) Hosts millions of open-source projects.
GitHub
51
(Git vs GitHub) It is the technology
Git
52
(Git vs GitHub) It is a platform that uses Git
GitHub
53
Git Definition: Code stored on your device
Local Repository
54
Git Definition: A cloud-hosted copy for collaboration
Remote Repository
55
Git Definition: Preparing files before committing them
File Staging
56
Git Definition: Saving changes locally.
Git Commit
57
Git Definition: Uploading changes to a remote repository
File Push
58
Git Definition: Checking modified and staged files.
Git Status
59
Git Definition: Viewing commit history
Git Log
60
Git Definition: Combining different versions of code.
Merging
61
Git Definition: Proposing changes to a repository for review.
Pull Request