Version Control & Collaboration Flashcards

In a Git workflow, what is the role of a 'code owner' file (e.g., CODEOWNERS)?

Answer: It automatically assigns reviewers based on file paths when a pull request is opened

A CODEOWNERS file maps file patterns to responsible team members, causing the platform to auto-request reviews from those owners when the relevant files change in a PR.

What is semantic versioning (SemVer) and which format does it follow?

Answer: A three-part versioning scheme; format MAJOR.MINOR.PATCH

SemVer uses MAJOR.MINOR.PATCH where MAJOR increments on breaking changes, MINOR on backwards-compatible features, and PATCH on backwards-compatible bug fixes.

Which Git feature allows developers to save uncommitted changes temporarily without creating a commit?

Answer: git stash

git stash temporarily shelves uncommitted changes in a stack, allowing the developer to switch context and later restore those changes with git stash pop.

What is a 'fork' in the context of Git collaboration platforms like GitHub?

Answer: A copy of a repository in your own account, used to propose changes via pull requests

Forking creates a personal copy of another user's repository, enabling you to freely experiment and submit contributions back via pull requests without write access to the original.

What does 'git bisect' help a developer accomplish?

Answer: Identify the specific commit that introduced a bug using binary search

git bisect performs a binary search through commit history, marking commits as good or bad until it pinpoints the exact commit that introduced a regression.

In DevOps, what is the key advantage of using short-lived feature branches over long-lived feature branches?

Answer: Short-lived branches reduce merge conflicts and integrate feedback more frequently

Short-lived branches diverge from the main branch for a brief period, minimizing merge conflicts and enabling continuous integration of small, reviewable increments.

What is the purpose of a Git tag, and how does it differ from a branch?

Answer: A tag marks a specific point in history as immutable; a branch is a movable pointer to commits

Tags create a fixed, named reference to a specific commit (typically a release), while branches are mutable pointers that advance with each new commit.