Git

Question 1

Use git f____ to retrieve new work done by other people

Answer 1

Use git fetch to retrieve new work done by other people

Question 2

command you use to view the changes in the files you are going to commit

Answer 2

git diff

Question 3

view the changes in the staging area

Answer 3

git diff –cached

Question 4

If you seem to have lost your history, check the r____ as your safety net.

Answer 4

If you seem to have lost your history, check the reflog as your safety net.

git reflog

Question 5

To search the commit log for a text pattern:

Answer 5

git log –grep=”text here”

git log –grep=word

Question 6

output git log with the first line only

Answer 6

git log –oneline

Question 7

view the changes in all previous commits

Answer 7

git log -p

Question 8

discard all changes you made in the working tree

Answer 8

git restore .

Question 9

To unstage all files from the current change set:

Answer 9

git reset

Question 10

The major benefit of rebasing (over merging) is that you get a much cleaner project h_____

Answer 10

The major benefit of rebasing is that you get a much cleaner project history

Question 11

The golden rule of git rebase is to never use it on p____ branches.

Answer 11

The golden rule of git rebase is to never use it on public branches.

Question 12

So, before you run git rebase, always ask yourself, “Is anyone else looking at this branch?” If the answer is yes, take your hands off the keyboard and start thinking about a non-destructive way to make your changes (e.g., the git r____ command).

Answer 12

So, before you run git rebase, always ask yourself, “Is anyone else looking at this branch?” If the answer is yes, take your hands off the keyboard and start thinking about a non-destructive way to make your changes (e.g., the git revert command).

Question 13

If you would prefer a clean, linear history free of unnecessary merge commits, you should reach for git r____ instead of git merge when integrating changes from another branch.

Answer 13

If you would prefer a clean, linear history free of unnecessary merge commits, you should reach for git rebase instead of git merge when integrating changes from another branch.

Question 14

The git s___ command takes your uncommitted changes (both staged and unstaged), saves them away for later use, and then reverts them from your working copy

Answer 14

The git stash command takes your uncommitted changes (both staged and unstaged), saves them away for later use, and then reverts them from your working copy

Question 15

You can reapply previously stashed changes with git s____ p__

Answer 15

You can reapply previously stashed changes with git stash pop

Question 16

If you decide you no longer need a particular stash, you can delete it with git stash d___

Answer 16

If you decide you no longer need a particular stash, you can delete it with git stash drop

Question 17

git b____ is used to examine specific points of a file’s history and get context as to who the last author was that modified the line.

Answer 17

git blame is used to examine specific points of a file’s history and get context as to who the last author was that modified the line.

Question 18

The -_ option will perform a “dry run” of git clean. This will show you which files are going to be removed without actually removing them.

Answer 18

The -n option will perform a “dry run” of git clean. This will show you which files are going to be removed without actually removing them.

$ git clean -n
Would remove untracked_file

Question 19

The git revert command can be considered an ‘undo’ type command, however, it is not a traditional undo operation. Instead of removing the commit from the project history, it figures out how to invert the changes introduced by the commit and appends a new commit with the resulting inverse content. This prevents Git from losing h____, which is important for the integrity of your revision history and for reliable collaboration.

Answer 19

The git revert command can be considered an ‘undo’ type command, however, it is not a traditional undo operation. Instead of removing the commit from the project history, it figures out how to invert the changes introduced by the commit and appends a new commit with the resulting inverse content. This prevents Git from losing history, which is important for the integrity of your revision history and for reliable collaboration.

Question 20

Reverting should be used when you want to apply the i_____ of a commit from your project history. This can be useful, for example, if you’re tracking down a bug and find that it was introduced by a s____ commit. Instead of manually going in, fixing it, and committing a new snapshot, you can use git revert to automatically do all of this for you.

Answer 20

Reverting should be used when you want to apply the inverse of a commit from your project history. This can be useful, for example, if you’re tracking down a bug and find that it was introduced by a single commit. Instead of manually going in, fixing it, and committing a new snapshot, you can use git revert to automatically do all of this for you.

Question 21

Other ‘undo’ commands like, git checkout and git reset, move the H___ and branch ref pointers to a specified commit. Git revert also takes a specified commit, however, git revert does not move ref p_____ to this commit.

Answer 21

Other ‘undo’ commands like, git checkout and git reset, move the HEAD and branch ref pointers to a specified commit. Git revert also takes a specified commit, however, git revert does not move ref pointers to this commit.

Question 22

git revert is able to target an individual commit at an arbitrary point in the h____, whereas git reset can only work backward from the c____ commit.

Answer 22

git revert is able to target an individual commit at an arbitrary point in the history, whereas git reset can only work backward from the current commit.

Question 23

The git r____ command is a complex and versatile tool for undoing changes with three primary forms of invocation that correspond to command line arguments: –soft, –mixed, –hard

Answer 23

The git reset command is a complex and versatile tool for undoing changes with three primary forms of invocation that correspond to command line arguments: –soft, –mixed, –hard

Question 24

The three git reset arguments each (–soft, –mixed, –hard) correspond to Git’s three internal state management mechanism’s, The Commit Tree (HEAD), The Staging Index, and The Working Directory.

Answer 24

The three git reset arguments each (–soft, –mixed, –hard) correspond to Git’s three internal state management mechanism’s, The Commit Tree (HEAD), The Staging Index, and The Working Directory.

Question 25

git reset moves both the H____ and branch r___s to the specified commit.

Answer 25

git reset moves both the HEAD and branch refs to the specified commit.

Question 26

The default invocation of git reset has implicit arguments of –m____ and HEAD

Answer 26

The default invocation of git reset has implicit arguments of –mixed and HEAD

Question 27

Rebase itself has 2 main modes: “m____” and “i_____” mode

Answer 27

Rebase itself has 2 main modes: “manual” and “interactive” mode

Question 28

From a content perspective, rebasing is changing the base of your branch from one commit to another making it appear as if you’d created your branch from a different c_____.

Answer 28

From a content perspective, rebasing is changing the base of your branch from one commit to another making it appear as if you’d created your branch from a different commit.

Question 29

The git checkout command accepts a -__ argument that acts as a convenience method which will create the new branch and immediately switch to it.

Answer 29

The git checkout command accepts a -b argument that acts as a convenience method which will create the new branch and immediately switch to it.

git checkout -b ＜new-branch＞

Question 30

Passing the –m___ argument to the git log command will produce a log with a list of commits that conflict between the merging branches.

Answer 30

Passing the –merge argument to the git log command will produce a log with a list of commits that conflict between the merging branches.

Question 31

Executing git merge with the –a___ option will exit from the merge process and return the branch to the state before the merge began.

Answer 31

Executing git merge with the –abort option will exit from the merge process and return the branch to the state before the merge began.

Question 32

The git merge and git pull commands can be passed an -_ (strategy) option. The -_ option can be appended with the name of the desired merge strategy.

Answer 32

The git merge and git pull commands can be passed an -s (strategy) option. The -s option can be appended with the name of the desired merge strategy.

Question 33

The –g____ option draws an ASCII graph representing the branch structure of the commit history.

Answer 33

The –graph option draws an ASCII graph representing the branch structure of the commit history.

Question 34

see all config variables

Answer 34

git config -list