The git stash ________ command allows you to view all the stashed changes in the repository.

  • Apply
  • Drop
  • List
  • Pop
The correct option is c. List. The git stash list command displays a list of all stashed changes in the repository, showing their stash IDs and descriptions. It helps you identify and manage stashed changes.

How can you view the configuration settings of a Git repository?

  • git config
  • git info
  • git settings
  • git show
To view the configuration settings of a Git repository, you can use the git config command. This command shows both repository-specific and global configuration settings.

What are the best practices for managing a pull request in a large project?

  • Regularly update the branch, Provide clear commit messages, Review and discuss changes with the team, Resolve conflicts promptly
  • Automate the entire pull request process, Use vague commit messages to keep it simple, Avoid discussing changes with the team, Ignore conflicts
  • Prioritize personal coding style over project conventions, Keep the branch outdated to avoid conflicts, Delay conflict resolution, Perform code review after merging
  • Force push changes without discussion, Merge without testing, Ignore code style guidelines, Delay pull request approval
In a large project, managing pull requests involves regularly updating the branch to incorporate changes from the main branch, providing clear commit messages for better understanding, reviewing and discussing changes with the team to ensure code quality, and resolving conflicts promptly to avoid delays. These practices contribute to a smoother and more efficient collaboration process.

When collaborating on a project, you typically push your changes to the _______ branch of the remote repository.

  • master
  • main
  • origin
  • remote
By convention, when collaborating, changes are pushed to the master branch. However, note that some projects may use main as the default branch.

If you have committed the wrong files to Git, what command can you use to undo this last commit?

  • git reset --soft HEAD^
  • git revert HEAD
  • git reset --hard HEAD^
  • git reset HEAD^
The correct option, git reset --hard HEAD^, is also used in this scenario to completely undo the last commit along with the changes. It discards the commit and resets the branch pointer. Other options are for different use cases: preserving changes, creating a new commit to undo changes, and unstaging changes.

A development team is experiencing slow performance when working with a Git repository containing large binary files. What Git feature should they consider implementing?

  • Git LFS (Large File Storage)
  • Shallow clones
  • Git submodules
  • Git Hooks
The team should consider implementing Git LFS (Large File Storage) to efficiently handle large binary files. Git LFS is designed for versioning large files, preventing performance issues.

What are the implications of adopting a Git workflow in a distributed team with respect to continuous integration?

  • CI can become complex due to multiple branches
  • CI is not affected by distributed teams
  • Distributed teams have no impact on CI
  • CI is faster in distributed teams
Git Workflow and CI

In Git, __________ can be used to verify the integrity and origin of commits.

  • Hash
  • Signature
  • Tag
  • Branch
In Git, each commit is identified by a unique hash, which serves as its integrity check. The hash ensures that the commit's content and history haven't been altered, making it a reliable verification method.

Merging branches in Git typically involves the _______ branch into the current branch.

  • feature
  • master
  • development
  • source
When merging branches in Git, the changes from one branch are typically incorporated into another branch. The correct option is ' master'.

The process of systematically checking commits to find a bug using git ________ is known as bisecting.

  • Diff
  • Log
  • Bisect
  • Status
Git bisect is a powerful tool for pinpointing the introduction of bugs by systematically narrowing down the range of commits. It efficiently helps in identifying the commit where the bug was introduced.