Version ControlMedium#61What is Git, and how does it work?Git is a distributed version control system for tracking changes in source code, allowing collaborative work and branch management.
Version ControlHard#62Explain the difference between Git and SVN (Subversion).Git is distributed, with local repository copies; SVN is centralized, requiring network connectivity for repository access.
Version ControlMedium#63What is a merge conflict, and how do you resolve it in Git?Merge conflicts occur when changes in different branches clash. Resolve by manually editing files and committing the result.
Version ControlMedium#64Describe the purpose of branching in version control.Branching isolates development work without affecting other parts of the repository, aiding in feature development and experimentation.
Version ControlMedium#65What is a pull request (PR), and how does it work?A PR is a request to merge code from one branch to another, facilitating code review and discussion before integration.
Version ControlMedium#66How do you handle code conflicts in a team project?Resolve code conflicts through communication, careful review, manual merging, testing, and documenting resolutions.
Version ControlMedium#67What is code refactoring, and why is it important?Refactoring improves code structure and readability without altering functionality, enhancing maintainability and quality.
Version ControlMedium#68Explain the role of Git branching strategies like GitFlow.GitFlow organizes branches and releases, defining naming conventions and branch purposes for structured and organized development.
Version ControlHard#69What is Git rebase, and when would you use it?Git rebase re-applies commits onto another base for a cleaner history. Use with caution to maintain a linear project history.
Version ControlMedium#70Discuss the advantages of distributed version control systems.Distributed systems allow offline work, flexible branching/merging, faster operations, redundancy, and collaborative workflows.