Linked in quiz
LinkedIn Git quiz
# How can you check your current git version?
- [ ] git --v
- [x] git --version
- [ ] git --option
- [ ] git --current
# What command lets you create a connection between a local and remote repository?
- [ ] git remote add new
- [x] git remote add origin
- [ ] git remote new origin
- [ ] git remote origin
[Reference](https://stackoverflow.com/questions/20291731/how-to-connect-to-a-remote-git-repository)
# Describe what these Git commands do to the commit history:
```bash
git reset --hard HEAD~5
git merge --squash HEAD@{1}
```
- [ ] They reset the HEAD to the fifth commit in the repo, then merge to the master branch.
- [x] The current branch's HEAD is reset back five commits, then prior commits are squashed into a single commit.
- [ ] They delete the last five commits.
- [ ] They merge the last five commits into a new branch.
**Explanation:**
- `git reset --hard HEAD~5` resets the current branch to the commit just before the last 5 (see `man gitrevisions` for details about this notation and other cool alternatives like `HEAD@{2 days ago}`). As it is a hard reset, it will also overwrite every change in the working tree as well. See `man git-reset`.
- `git merge --squash HEAD@{1}` HEAD@{1} is where the branch was just before the previous command (again, see `man gitrevisions`). This command sets the state of the index to be as it would just after a merge from that commit. This whole operation could be a way to take 5 commits from a branch in which you started a new feature and squash them to a single commit, a meaningful one.
# Your current project has several branches; master, beta, and push-notifications. You've just finished the notification feature in the push-notification branch, and you want to commit it to beta branch. How can you accomplish this?
- [ ] Checkout the push-notifications branch and run git merge beta
- [ ] Checkout the master branch and run git merge beta -> push-notification
- [ ] Delete the push-notification branch and it will be committed to the master branch automatically
- [x] Checkout the beta branch and run git merge push-notification
# Which of the following is true you when you use the following command?
`git add -A`
- [x] All new and updated files are staged
- [ ] Files are staged in alphabetical order.
- [ ] All new files are staged
- [ ] Only updated files are staged
# What will the following command print to the Terminal?
`git remote -v`
- [x] A list of remote repositories and their URLs
- [ ] The current git version you're running
- [ ] An inline editor for modifying remote repositories
- [ ] The last 5 git versions you've installed
# Looking at the following commands, describe what is happening.
```bash
git checkout feature-user-location
git cherry-pick kj2342134sdf090093f0sdgasdf99sdfo992mmmf9921231
```
- [ ] The commit is being tagged for release on the feature-user-location branch
- [ ] A commit is being copied from its original branch over to the feature-user-location branch
- [x] The commit is being cherry picked as the new HEAD of the commit history
- [ ] A commit is being copied from the feature-user-location branch to the master branch
- [ ] The branch is switched to the feature-user-location branch, and the specified commit is applied to the branch.
**Explanation:** Commits aren't copied when cherry picking, they are cherry picked. The changes introduced by the commit are applied and a new commit is then created. This allow us to get specific changes as if they were patches (in the GIT's book, this is actually called [Patching](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Patching "See this in the GIT's book")). As a new commit is created upon feature-user-location, HEAD also changes to match it. You can see this in `cat .git/HEAD` and `cat .git/refs/heads/feature-user-location` for this case. See `man git-cherry-pick` for details.
**NOTE**: There are two versions of this question so far. The task is always "describe what is happening", the commands are always a `checkout` and a `cherry-pick`, and the correct answer is always the same.
# What does the following command do to the git repository?
`git reset --soft HEAD^`
- [ ] It deletes all previous commits and reset the repository history back to its initial state.
- [ ] It resets the working branch to the first commit.
- [ ] It keeps the HEAD at the current commit, but clears all previous commits.
- [x] It sets HEAD to the previous commit and leaves changes from the undone commit in the stage/index.
# You find a bug in your project, but can't locate where it was introduced in the commit history. How would you diagnose this problem?
- [ ] Manually backtrack through your commit history.
- [ ] Use git search -diff to compare all commits in your repository history.
- [ ] Run a git rebase to find the buggy commit.
- [x] Use git bisect to compare the buggy commit to an early commit that works as expected.
# Why would the following command be used?
`git rebase -i HEAD~10`
- [ ] To run a comparative search of the last 10 commits for differences
- [x] To list the last 10 commits and modify them with either the squash or fixup command
- [ ] To delete the last 10 commits and reset the HEAD
- [ ] In order to locally cache the last 10 commits
# Why would you use a pre-receive hook in your remote repository?
- [ ] You wouldn't, you would use it in the local repository
- [x] To execute a script when a remote receives a push that is triggered before any refs are updated
- [ ] To fire a script after updates are made to the remote repository
- [ ] To debug all commit tags and release versions
# What option can you use to apply git configurations across your entire git environment?
- [ ] `--all`
- [ ] `--master`
- [x] `--global`
- [ ] `--update`
# How could you squash multiple commits together without using git merge --squash?
- [ ] Caching
- [ ] You can't. git merge --squash is the only git command for that operation.
- [x] Rebasing
- [ ] Reflogging
# If you cloned an existing git repository, what would happen?
- [ ] A new copy would overwrite the central repository
- [x] A copy of the repository would be created on your local machine
- [ ] Nothing, cloning is not a supported git function
- [ ] A copy of the repository would be created on the hosting platform
# How can you display a list of files added or modified in a specific commit?
- [ ] Find the commit in the remote repository, as that's the only place that kind of information is stored.
- [x] Use the `diff-tree` command with the commit hash.
- [ ] Run `git commit --info` with the commit hash.
- [ ] Access the commit stash data with `git stash`.
# What files is this .gitignore programmed to leave out?
```shell
#.swift
build/
*.txt
*.metadata
```
- [ ] All files with a .swift, .txt, or metadata file extension, as well as the entire build directory
- [ ] Only the build directory
- [x] All files in the build directory, as well as files ending with .txt or .metadata
- [ ] Only files with .swift and .txt extensions.
A line starting with `#` serves as a comment. Hence `# .swift` does not do anything. See `man gitignore`.
# After you make changes to a local repository, you run the following command. What will this do?
`git commit -a -m "Refactor code base"`
- [ ] Nothing, you can't use multiple options in the same command
- [ ] Adds all new files to the staging area
- [ ] Commits all new files with a message
- [x] Adds all modified files to the staging area, then commits them with a message
# After checking your git status you get the following output, which shows the file beta-notes.js in the commit but also unstaged. How can this situation occur?
```shell
Change to be committed:
(use "git reset HEAD ..." to unstage)
modified: beta-notes.js
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout --..." to discard changes in working directory)
modified: beta-notes.js
```
- [ ] There were two copies of beta-notes.js but one was deleted
- [x] beta-notes.js was staged, then modified afterwards, creating two different versions of the file
- [ ] Two copies of beta-notes.js were created, but only one is being tracked
- [ ] There are two tracked copies of beta-notes.js, but one was removed from the commit
# Where are files stored before they are committed to the local repository?
- [ ] Saved files
- [ ] git documents
- [x] Staging area
- [ ] git cache
# What commands would you use to force an overwrite of your local files with the master branch?
- [ ] ⠀
```bash
git pull --all
git reset --hard origin/master
```
- [ ] ⠀
```bash
git pull -u origin master
git reset --hard master
```
- [ ] ⠀
```bash
git pull origin master
git reset --hard origin/myCurrentBranch
```
- [x] ⠀
```bash
git fetch --all
git reset --hard origin/master
```
- The command `pull` is `fetch` followed by either `merge` or `rebase` (in this case, `merge`). We don't want to merge. Merge would be an action to our **repository**. We just want to overwrite our **local files**.
# Which statement is true when you use the git add -A command?
- [ ] Only new files in the working directory are staged to the index.
- [x] All new and updated files from the working directory are staged to the index.
- [ ] All files in the working directory are staged to the index in alphabetical order.
- [ ] Only updated files in the working directory are staged to the index.
# You find that your project has a tag and branch both named push-notifications, which causes confusion when trying to print out given reference. How can you specify which branch you want to look at?
- [ ] use git show refs/push-notifications
- [ ] use git show push-notifications
- [ ] use git show heads/refs/push-notifications
- [x] use git show refs/heads/push-notifications
[Reference](https://geedew.com/fixing-git-branch-and-tag-name-collision/)
# Your team lead needs a list of all commits that will be moved before you perform a rebase. Which command can you use to access that information?
- [ ] git rebase -log
- [x] git rebase -i
- [ ] git rebase -verbose
- [ ] git rebase -all
# What is the operation doing given the Git commands below?
```
git bisect start
git bisect bad 5d41402abc4b2a76b9719d911017c592
git bisect good 69faab6268350295550de7d587bc323d
```
- [ ] It runs a merge of a good commit that is discovered using a known bad commit and known good commit
- [ ] It marks a commit for deletion using a known bad commit and known good commit to determine which commit introduced a bug
- [ ] It defines a bad commit and resets the HEAD using a known bad commit and known good commit
- [x] It performs a binary search using a known bad commit and known good commit to determine which commit introduced a bug
# In a situation where you have several commits for a single task, what is the most efficient way to restructure your commit history?
- [ ] Cherry pick the related commits to another branch.
- [ ] Delete the task commits and recommit with a new message.
- [x] Squash the related commits together into a single coherent commit.
- [ ] Stash the related commits under a new hash.
# Which of the following is true of the git push command?
- [x] By default a push doesn't send tags to the remote repository.
- [ ] Commits can only be tagged when they are created.
- [ ] Tags are pushed to the remote repository with their respective commits.
- [ ] Only annotated tags are automatically pushed to the remote repository with a commit.
[Reference](https://git-scm.com/book/en/v2/Git-Basics-Tagging#_sharing_tags)
# After pushing commits to the remote repository for the first time using the command below, what shorthand command can you use in future?
```bash
git push -u origin master
```
- [ ] git push master
- [ ] git push origin
- [ ] Same as before, git push -u origin master
- [x] git push
# How would you create a custom shortcut or command across your git environment?
- [ ] Run git hotfix with the shortcut name.
- [ ] Assign a shortcut or command using git options file.
- [ ] Use the git custom-key command.
- [x] Create an alias using the git config command.
# What is the status of the beta-notes.js file in the following output?
```shell
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: beta-notes.js
```
- [ ] beta-notes.js is untracked and has been modified.
- [x] beta-notes.js is a tracked file and has been modified, but has not been added to the current commit.
- [ ] beta-notes.js is untracked but has been added to the current commit.
- [ ] beta-notes.js is tracked, and the modified file has been added to the current commit.
# What command would let you modify your previous commit?
- [ ] --fix
- [ ] --quickfix
- [ ] --modify
- [x] --amend
# What is the best way to characterize the git commit structure?
- [ ] Data array
- [x] Data log
- [ ] Data snapshot
- [ ] Data dictionary
# What change will the following command make to the staging area files?
`git rm --cached testfile.js`
- [x] testfile.js will be removed from the staging area and its changes no longer tracked.
- [ ] testfile.js will be removed from the staging area but its changes will still be tracked.
- [ ] A copy of testfile.js will be cached on your desktop.
- [ ] The current copy of testfile.js will be saved in the staging area.
# After you've successfully merged two branches and committed the changes, what is the next step in keeping your git structure organized?
- [ ] Use the git reset --soft HEAD to roll back one commit.
- [x] Run git branch -d `` to delete the merged branch.
- [ ] Use git clear-all to clean up any hanging files.
- [ ] Run git rebase to move the current commit to its original location.
# While modifying a file, you're unexpectedly assigned an urgent bug fix on another branch. How can you temporarily save your local work without committing?
- [ ] This is not possible, as you cannot save locally without committing.
- [ ] Run git hold to save a local copy of what you're doing to return to later.
- [ ] Save your work with git local-cache.
- [x] Use git stash to save your work and come back later and reapply the stashed commit.
# What command would you use to create a new git repository?
- [ ] git add
- [ ] git start
- [ ] git new
- [x] git init
# While working on a feature branch you try to use "git rerere" to solve a recurring merge conflict but nothing is happening. What could be causing this issue?
- [ ] The "-all" option isn't added to the command.
- [x] "rerere.enabled" isn't enable in the config file.
- [ ] The commit hash is missing.
- [ ] The filepath isn't specified.
# Which setting determines what pager is used when Git pages output?
- [ ] core.page
- [ ] page
- [ ] pager
- [x] core.pager
# What does commit object contain?
- [ ] A set of files, representing the state of a project at a given point of time.
- [ ] Reference to parent commit objects.
- [x] An SHA1 name, a 40-character string that uniquely identifies the commit object.
# Which option enables inclusion of committer name in custom log format?
- [ ] %ce
- [ ] %cr
- [ ] %cd
- [x] %cn
# How many ways are present in Git to integrate changes from one branch into another?
- [ ] 3
- [ ] 5
- [x] 2
- [ ] 4
[Reference link](https://git-scm.com/book/en/v2/Git-Branching-Rebasing)
`In Git, there are two main ways to integrate changes from one branch into another: the merge and the rebase.`
# Which user should be created first during setting up of SSH?
- [x] git
- [ ] admin
- [ ] root
- [ ] None of these
# Which command will list tags with the 1.4.2 series?
- [ ] git tag 'v1.4.2'
- [x] git tag -I 'v1.4.2.\*'
- [ ] git tag-list 'v1.4.2\*'
- [ ] git tag 'v1.4.2\*'
# Which of the following is an integration manager?
- [ ] lieutenants
- [x] benevolent dictator
- [ ] Depends upon project type
- [ ] Depends upon data
# Which Git command begins tracking of a new file?
- [x] add
- [ ] addfile
- [ ] begin
- [ ] track
# Which of the following is called dumb protocol?
- [ ] All of these
- [ ] SSH
- [ ] Git
- [x] HTTP
# Which key press returns a set of suggestions to pick from, when writing a Git command?
- [ ] Control
- [ ] Shift
- [x] Tab
- [ ] Alt
# Which of these terms best describes Git?
- [x] Distributed Version Control System
- [ ] Issue Tracking System
- [ ] Integrated Development Environment
- [ ] Web-Based Repository Hosting Service
# Which command gets a copy of an existing Git repository?
- [ ] duplicate
- [ ] replicate
- [ ] copy
- [x] clone
# How does Git think of its data?
- [ ] File
- [ ] None of these
- [x] Snapshot
- [ ] Folder
# Which option enables inclusion of author name in custom log format?
- [ ] %am
- [ ] %ad
- [ ] %ae
- [x] %an
# Which version onwards did Git offer reversing a file back to what it looked like when last committed?
- [ ] 1.7
- [x] 1.6
- [ ] 2.0
- [ ] 1.8
# Which strategy is used by Git for merging two branches?
- [ ] LIFO
- [x] recursive
- [ ] FIFO
- [ ] octopus
# What does refs store?
- [x] SHA-1 value
- [ ] None of these
- [ ] Branch name
- [ ] Project name
# What Language is used in GIT?
- [x] C
- [ ] C++
- [ ] C#
- [ ] Java
# What is usually the extension of file which has the public key?
- [ ] ssh
- [x] pub
- [ ] key
- [ ] pk
# What is the difference between initializing a normal repo and a bare repo?
- [ ] Bare repos store their git history in a .git subfolder.
- [ ] Bare repos do not have the .git extension.
- [x] Bare repos do not come with working or checked-out source files.
- [ ] Bare repos should be used for local rather than remote repos.
# How many individual commits can a single repository have?
- [x] any number of commits
- [ ] only one commit local per repository
- [ ] only three commits per branch
- [ ] only one commit per HEAD
# What types of tags does Git support?
- [ ] heavy and concise
- [ ] lightweight and immutable
- [ ] heavy and annotated
- [x] lightweight and annotated
# After staging a series of changes to the index, which command could you use to review them prior to a commit?
- [x] git diff --cached
- [ ] git diff
- [ ] git diff --HEAD
- [ ] git status -v -v
# What does the git stash drop command do?
- [x] removes the most recent stash entry
- [ ] deletes the stash
- [ ] lists everything in the stash
- [ ] throws away the oldest entry
# What command creates a new branch from the currently checked-out branch?
- [ ] `git -b checkout `
- [ ] `git branch`
- [ ] `git checkout `
- [x] `git checkout -b `
# After mistakenly staging a file named myFile to the index, how would you remove it from the index to exclude it from your next commit?
- [ ] Use git reset HEAD^.
- [x] Use git reset myFile.txt.
- [ ] Use git -rm myFile.txt.
- [ ] Use git reset.
# What happens if you run this command from your master branch?
```bash
git checkout -b beta-test
```
- [ ] The beta-test branch will be checked out of the current commit.
- [ ] The beta-test branch will be checked out and deleted.
- [x] A new branch called beta-test will be created and switched to.
- [ ] The beta-test branch will be merged with the master branch.
# How does Git internally manage branches?
- [x] by creating a pointer to the most recent snapshot/commit for the branch.
- [ ] by creating a data array of branches in the same repository.
- [ ] by creating a data dictionary of code changes.
- [ ] be creating a debug log that stores repository changes.
# You want to perform a git reset but cannot recall all of the available options. What command would you use to see a description of them?
- [x] git help reset
- [ ] git -h reset
- [ ] git options reset
- [ ] git reset help
# What is a remote repository?
- [ ] a version of the repository that mirrors changes made in the local repository's master branch for open-source collaboration efforts
- [ ] the lead repository elected by the Git arbitrator found within local repositories of collaborating team members
- [ ] a read-only version of the repository stored on a backup server in case local repositories become lost or corrupted
- [x] a version of the repository hosted on the internet or network that is pushed to or pulled from by collaborators
# After modifying some existing files in a repository, you decide to discard the changes. What command can you use?
- [x] git restore
- [ ] git undo
- [ ] git clean
- [ ] git checkout
# After starting to merge a feature branch into your master branch, you encounter a merge conflict and decide you do not want to perform the merge. How can you stop the merge and restore to the pre-merge state?
- [ ] Use git restore -p.
- [ ] Use git merge -u.
- [x] Use git merge --abort.
- [ ] Use git merge --undo.
# If you have several commits for a single feature, what is the most efficient way to restructure your commit history?
- [ ] Use git stash to consolidate the commits under a new hash.
- [x] Use git squash to consolidate the commits together into a single coherent commit.
- [ ] Delete the task commits and recommit with a new message.
- [ ] Use git cherry-pick to place the commits in another branch.
# Which command correctly creates a lightweight tag?
- [x] `git tag v3.8.1`
- [ ] `git tag --light "v3.8.1"`
- [ ] `git tag v3.8.1 —-annotate -m ""`
- [ ] `git tag -l v3.8.1`
# What is the main issue with using git rebase when working with multiple developers?
- [ ] Rebase affects only your repository and creates a diff in the master branch.
- [ ] Rebase creates a temporary copy of the master branch in the remote repo.
- [ ] Rebase moves the HEAD of the remote master branch one commit forward.
- [x] Rebase deletes all commit history for the new feature branch.
# What Git workflow is used by teams that collaborate on a single branch and avoid creating long-lived development branches?
- [ ] Git flow
- [ ] Mainline flow
- [x] Trunk-Based Development
- [ ] GitHub flow
# Which option on the git log command allows you to limit output to commits made after certain date?
- [x] `--since`
- [ ] `--sinceWhen`
- [ ] `-`
- [ ] `--afterDate`
# How would you delete unreachable objects older than a specified time from your project database?
- [ ] `git cache --obsolete
About Us
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.
Know More