During a project audit, you need to find out when a specific bug was introduced. What Git feature can help you trace the origin of this bug?
- blame
- log
- bisect
- show
The correct option is bisect. The git bisect command allows you to perform a binary search through the commit history to identify when a bug was introduced. By marking good and bad commits, Git efficiently narrows down the faulty commit range.
A pull request is a request to merge a branch called _______ into another branch in a Git repository.
- feature_branch
- source_branch
- target_branch
- merge_branch
In a pull request, the branch to be merged is the target branch, where the changes will be applied.
After completing a significant feature, a developer wants to mark the current state of the repository for future reference. Which Git feature would be most appropriate?
- Tag
- Branch
- Commit
- Stash
The correct option is Tag. Tags in Git are used to mark specific points in history as being important. This is commonly done to capture a release point or mark a significant version in the repository. Unlike branches, tags are generally not moved once created.
What is the main benefit of conducting code reviews before merging changes?
- Identifying and fixing bugs and issues early in the development process.
- Speeding up the merging process without thorough examination.
- Adding unnecessary complexity to the codebase.
- Code reviews are optional and don't impact the development workflow.
Code reviews help in early bug detection and ensure that the proposed changes meet coding standards. They contribute to better code quality, knowledge sharing among team members, and overall project maintainability.
For advanced CI/CD workflows, Git's ________ feature can be used to manage code reviews effectively.
- Pull Request
- Stash
- Rebase
- Bisect
In Git, the feature used for managing code reviews effectively in advanced CI/CD workflows is the Pull Request. Pull Requests provide a structured way for team members to review and discuss changes before merging them into the main codebase. This is crucial for maintaining code quality and collaboration in larger projects.
In Git, a release is often marked with a ________, representing a stable point in the development.
- Tag
- Stash
- Branch
- Commit
In Git, a release is commonly marked with a tag. Tags are labels for specific points in Git history, often used to represent stable versions of the software.
Which Git feature is commonly used to trigger a CI/CD pipeline?
- Git Hooks
- Git Stash
- Git Submodules
- Git Branches
Git Hooks are scripts triggered by specific Git events, making them suitable for CI/CD pipeline triggers. Stash, submodules, and branches serve different purposes in Git but are not directly tied to CI/CD.
After reviewing a repository's history, a team leader finds an unauthorized access. What Git practice could have prevented this?
- Branch protection
- Code signing
- Git hooks
- Commit squashing
Branch protection can prevent unauthorized access by defining rules that restrict certain actions on specific branches. By enforcing access controls, the team leader could have prevented unauthorized changes and maintained a secure repository.
What is the purpose of the git commit command?
- Save changes to the local repository
- Upload changes to the remote repository
- Discard local changes
- Create a new branch
The purpose of the git commit command is to save changes to the local repository. It creates a new commit with the changes you have made, providing a way to track the history of your project.
To ignore certain files from being tracked in Git, list them in a _______ file.
- .exclude
- .gitignore
- exclude.txt
- ignorefile
The correct option is "b) .gitignore." The .gitignore file is used to specify files or patterns that Git should ignore. This helps in preventing unnecessary files from being tracked, such as temporary files or compiled binaries.