Version Control Flashcards
What is Version Control?
Version control is the management of changes to source code or files, allowing multiple contributors to work on a project while keeping track of modifications, history, and versions of files.
Why is Version Control important?
Version control is essential for collaborative software development, ensuring that changes are tracked, conflicts are managed, and teams can work on code simultaneously without overwriting each other’s work.
What are the benefits of Version Control?
- Tracks changes to files over time. 2. Allows collaboration among multiple developers. 3. Prevents loss of data. 4. Enables rollbacks to previous versions. 5. Enhances team coordination and accountability.
What is a Version Control System (VCS)?
A Version Control System (VCS) is a tool that helps manage changes to code, track revisions, and allow for collaboration among developers. It helps maintain a history of the project and coordinates efforts from multiple contributors.
What is the difference between Centralized and Distributed Version Control?
In centralized version control, there is a central repository where code is stored, and developers check out and commit changes to this central server. In distributed version control, each developer has a complete copy of the repository, allowing for more flexibility and offline work.
What are the key types of Version Control?
- Centralized Version Control (CVCS) 2. Distributed Version Control (DVCS)
What is Centralized Version Control (CVCS)?
In CVCS, there is one central repository where all project files are stored, and developers must check out files from this repository to make changes and then check them back in.
What is Distributed Version Control (DVCS)?
In DVCS, every contributor has a local repository and full version history, allowing developers to work offline and later sync with the main repository. Changes are typically merged from different repositories.
What are some key Version Control technologies?
- Git 2. Subversion (SVN) 3. Mercurial (Hg) 4. Perforce 5. CVS (Concurrent Versions System)
What is Git?
Git is a distributed version control system that allows multiple developers to track changes in files, work offline, and merge changes easily. It is highly flexible and widely used in modern software development.
What are the key features of Git?
- Distributed architecture 2. Branching and merging capabilities 3. Staging area for commits 4. Efficient handling of large projects 5. Open-source and widely supported
What is Subversion (SVN)?
Subversion (SVN) is a centralized version control system that manages changes to files and directories over time, allowing multiple users to collaborate on projects.
What are the key features of SVN?
- Centralized repository 2. Simple branching and merging 3. Versioned directories and metadata 4. Supports binary files 5. Works well for smaller teams or centralized workflows
What is Mercurial (Hg)?
Mercurial (Hg) is a distributed version control system, similar to Git, but with a simpler interface. It allows users to track changes, create branches, and manage version history.
What are the key features of Mercurial?
- Distributed architecture 2. Simple command-line interface 3. Fast and efficient handling of changes 4. Lightweight and easy to learn 5. Provides branching and merging
What is Perforce?
Perforce (Helix Core) is a version control system known for its high performance and scalability, often used in large enterprises or with teams handling large binary files, such as game development studios.
What are the key features of Perforce?
- Centralized version control 2. High performance with large binary files 3. Scalability for large teams 4. Extensive branching and merging tools 5. Integration with various build and CI tools
What is CVS (Concurrent Versions System)?
CVS is one of the oldest version control systems, offering centralized version control with support for handling multiple versions of files and directories, though it is less commonly used today.
What are the key features of CVS?
- Centralized version control 2. Branching and merging support 3. Tracking of file changes and versions 4. Historical revisions of files 5. Can be integrated with other development tools
What is the importance of Branching in Version Control?
Branching allows developers to work on different features or fixes independently of the main codebase, ensuring that changes don’t interfere with each other and can be merged later without conflict.
What is Merging in Version Control?
Merging is the process of combining changes from different branches into a single codebase. This is essential when multiple developers are working on different features or bug fixes simultaneously.
What is a Commit in Version Control?
A commit is a recorded change to the repository, capturing the state of the files at a particular point in time. It includes a description of the change and a reference to the user who made it.
What is a Pull Request?
A pull request is a way to propose changes to the main codebase. It allows developers to review changes, discuss modifications, and merge them into the project after approval.
What is a Version Control Branch?
A branch is a separate line of development that allows changes to be made independently from the main codebase, often used for features, bug fixes, or experiments.
