13.3.2 Version control

• Version control is a system that records changes to a file or set of files over time
• Which version control system is widely used and distributed?

  Git
• Subversion (SVN) is a centralized version control system
• Version control allows developers to track who made changes and why
• Branching in version control allows creating separate lines of development for bug fixes
• What ensures no work is lost when using Git in team projects?

  Merging to a central repository
• Order the key benefits of version control

  1️⃣ Track Changes

  2️⃣ Collaboration

  3️⃣ Rollback

  4️⃣ Branching
• Why is Git preferred for open-source projects?

  Efficient branching and distributed nature
• Subversion (SVN) is often used in enterprise environments where centralized control is desired
• Git uses a distributed architecture, while SVN uses a centralized architecture
• Version control allows developers to easily restore previous versions
• Branching in version control creates separate development lines for new features or fixes.
• Git uses a distributed architecture.
• Git is faster than Subversion (SVN).
• Git provides full offline access.
• Order the following version control systems by their popularity:

  1️⃣ Git

  2️⃣ Subversion (SVN)

  3️⃣ Mercurial
• Subversion (SVN) is often used in enterprise settings where centralized control is desired.
• Git offers efficient and easy branching.
• Git is the most popular version control system.
• Match the version control operation with its description:

  Commit ↔️ Saves changes to the local repository

  Push ↔️ Uploads local changes to the remote repository

  Pull ↔️ Downloads changes from the remote repository to local

  Branch ↔️ Creates a new line of development

  Merge ↔️ Combines changes from one branch into another
• Committing code frequently allows for incremental progress.
• Frequent commits create a comprehensive audit history.
• Committing code frequently improves collaboration among team members.
• Version control allows multiple developers to work on the same codebase.
• Order the key benefits of using version control:

  1️⃣ Track Changes

  2️⃣ Collaboration

  3️⃣ Rollback

  4️⃣ Branching
• Version control records every modification, user, and reason for changes.
• Version control is essential for systematic problem solving.
• Mercurial is often used for personal projects.
• The `git commit` operation saves changes to the local repository.
• Frequent commits make small changes easier to track and understand.
• What does the `git commit` operation do in version control?

  Saves changes locally
• The `git push` operation uploads local changes to the remote repository.
• What does the `git pull` operation achieve in version control?

  Downloads remote changes
• The `git branch` operation creates a new line of development in version control.
• What is the purpose of the `git merge` operation in version control?

  Combines branch changes
• Committing code frequently allows for incremental progress in version control.
• What is one advantage of committing code frequently in version control?

  Easy rollback
• How does frequent committing improve collaboration in version control?

  Facilitates seamless integration
• Committing code frequently provides a comprehensive history of modifications in version control.
• The Gitflow branching strategy uses multiple branches, including `master`, `develop`, and `feature`, to manage releases and ongoing development.