Which command is used to create a new Git repository?
- git create
- git init
- git new
- git start
The correct command to create a new Git repository is git init. This initializes a new repository in the current directory, preparing it for version control. Other options provided are not standard Git commands for creating a repository.
In learning from Git failures, it's often found that improper management of ________ can lead to significant issues.
- branches
- repositories
- merge conflicts
- permissions
Improper management of merge conflicts can lead to significant issues in Git. Merge conflicts arise when changes in different branches cannot be automatically merged. Proper conflict resolution and communication are essential to avoid disruptions in the development process.
A 'detached HEAD' state in Git occurs when you check out a specific _______ instead of a branch.
- Commit
- Tag
- Remote
- Branch
A 'detached HEAD' state occurs when you check out a specific commit instead of a branch. In this state, you are no longer on any branch, and any new commits will not be associated with a branch, potentially leading to data loss if not handled carefully.
The command git _______ can be used to find a list of all commits that could be causing a merge conflict.
- history
- log
- blame
- diff
The git log command is used to view the commit history. By examining the log, you can identify the commits that may be causing a merge conflict.
In what scenario is rebasing preferred over merging in Git?
- Rebasing is preferred when working on a feature branch that you want to keep clean and incorporate the latest changes from the main branch.
- Rebasing should be used when there are conflicts between branches to create a new, unified commit.
- Rebasing is suitable only for small projects with a limited commit history.
- Rebasing is recommended when you want to preserve the existing branch structure and history.
In-depth Rebasing is beneficial for creating a linear history, especially when working on feature branches, to avoid unnecessary merge commits.
During a code review, a team member identifies an issue that could potentially break the build. What Git feature allows for collaborative discussion and resolution?
- Git Stash
- Git Revert
- Git Bisect
- Git Comments
Git Comments allow collaborative discussion during code reviews. Developers can comment on specific lines of code, addressing issues, proposing solutions, and ensuring a smooth resolution process.
The ________ command in Git is commonly used to propose changes in a collaborative project.
- Commit
- Push
- Merge
- Pull
The "Push" command in Git is used to propose changes in a collaborative project by uploading the local changes to a remote repository. This is a crucial step in sharing code with others.
When cherry-picking a commit, Git creates a new commit with a different ________ even if the content is the same.
- Hash
- Branch
- Message
- Timestamp
When cherry-picking a commit in Git, it generates a new commit with a different hash to maintain uniqueness, even if the content is identical. The hash is a cryptographic checksum of the commit, and altering the commit creates a new hash.
In the Gitflow workflow, the ________ branch contains the official release history.
- Master
- Develop
- Release
- Hotfix
In Gitflow, the "Release" branch contains the official release history, and it is where code freezes in preparation for a new release. This branch helps manage versioning effectively.
Which Git Hook is triggered before a commit is finalized?
- pre-commit
- post-commit
- pre-receive
- post-receive
The pre-commit hook is triggered before a commit is finalized. It allows you to inspect the changes that are about to be committed and optionally abort the commit. This hook is useful for tasks like code formatting or running pre-commit tests.