In a code review, checking for _______ and _______ is essential to maintain code quality.
- syntax errors, performance issues, formatting, logic errors
- documentation, security vulnerabilities, formatting, functionality
- syntax errors, performance issues, documentation, security vulnerabilities
- formatting, code complexity, security vulnerabilities, logic errors
In a code review, it's crucial to check for documentation and security vulnerabilities to ensure not only the correctness of the code but also its readability and safety.
The command git __________ is useful for reducing the size of a repository by removing unnecessary data.
- gc
- prune
- cleanup
- compress
The 'git gc' command (garbage collection) is used to optimize and clean up the local repository by removing unnecessary data, reducing its size.
How can advanced rebasing techniques be used to resolve complex merge conflicts in Git?
- git merge-base
- git rebase -i
- git cherry-pick
- git reset
Advanced rebasing can be performed using git rebase -i, allowing you to interactively choose how to apply and modify commits. This helps in resolving complex merge conflicts by providing a more granular approach to handle changes.
What is the basic benefit of using Git for database version control?
- Enables tracking of changes to database schema and data
- Enhances database performance
- Provides real-time database monitoring
- Automates database backups
Git benefits database version control by enabling the tracking of changes to database schema and data. This ensures version history and facilitates collaboration in database development.
A tag in Git is like a bookmark to a specific ________ in the repository's history.
- branch
- commit
- file
- pull request
The correct option is b) commit. A tag in Git is a reference to a specific commit in the repository's history. It serves as a permanent marker for a specific point in time, often used to mark release points.
In large projects, Git's __________ feature is crucial for managing different development streams.
- Rebase
- Merge
- Branch
- Stash
Git's branching feature is crucial in large projects as it allows developers to work on different development streams concurrently. Each branch can represent a specific feature or bug fix, making it easier to manage and merge changes later.
How do branch protection rules contribute to repository security?
- Prevent force pushes to protected branches
- Restrict branch deletion
- Control who can merge to certain branches
- All of the above
Branch protection rules enhance repository security by preventing force pushes, restricting branch deletion, and controlling who can merge to specific branches. However, the options provided do not include the correct answer.
A team notices that their feature branch is several commits behind the main branch. What Git strategy should they employ to update their branch without cluttering the commit history?
- Merge the main branch into the feature branch
- Rebase the feature branch onto the main branch
- Cherry-pick the changes from the main branch and apply to the feature branch
- Create a new branch from the main branch and merge it into the feature branch
To update a feature branch without cluttering the commit history, it's advisable to use rebase. This integrates the latest changes from the main branch into the feature branch, maintaining a linear history and avoiding unnecessary merge commits.
In Git, what is the result of executing a 'merge' command?
- Creates a new branch
- Combines changes from different branches
- Deletes a branch after merging
- Reverts all changes made in a branch
The 'merge' command in Git combines changes from different branches into the current branch. It integrates the changes, creating a new commit that represents the combined state of the branches.
What is the purpose of cherry-picking in Git?
- Apply specific commits
- Merge two branches
- Revert changes
- Delete a branch
Cherry-picking in Git allows you to select specific commits from one branch and apply them to another. This is useful when you only want certain changes from one branch without merging the entire branch.
In a collaborative project using Git, what is the purpose of a pull request?
- A pull request is a mechanism for contributors to propose changes to the main repository and request that someone review and merge their changes.
- Pull requests are used to fetch changes from a remote repository.
- Pull requests are only necessary in Forking workflow, not in Feature Branch workflow.
- Pull requests are equivalent to merge requests and are used only for merging code.
Pull requests facilitate code review, discussion, and automated testing before changes are merged into the main branch, promoting collaboration and maintaining code quality.
To automate the execution of tests every time a new commit is pushed, a _________ Git hook can be utilized.
- Pre-receive
- Post-receive
- Update
- Pre-commit
Git hooks are scripts that Git executes before or after events such as commit, push, and receive. The Post-receive hook is suitable for automated tasks after a successful push.