Kostas Diakogiannis
Quiz von , erstellt am more than 1 year ago

A 16 Questions basic self-assessment test regarding git and github workflow. Thus the participants can estimate how good they have proceeded with git, how further they need to go. Also for the teacher is a good tool for solving the commonest misconceptions on the spot.

179
0
0
Kostas Diakogiannis
Erstellt von Kostas Diakogiannis vor etwa 6 Jahre
Schließen

Git self assesment Quiz

Frage 1 von 16

1

How can someone convert a normal folder with name my_project into a local git repository?

Wähle eine der folgenden:

  • Git merge my_project

  • Git remote add origin my_project

  • Git init

  • Git push origin my_project

Erklärung

Frage 2 von 16

1

When someone clones a remote repository to his computer, this automatically gives him the access to change the code to the files in his computer and to push his code back to remote again.

Wähle eins der folgenden:

  • WAHR
  • FALSCH

Erklärung

Frage 3 von 16

1

What is the ultimate prerequisite for someone in order to perform a commit?

Wähle eine der folgenden:

  • Having the file changes stashed.

  • Having just changed some files.

  • Having the changed file also staged.

Erklärung

Frage 4 von 16

1

Select the correct order of the actions , that have to be made if someone wants to send his code to remote from the beginning.

Wähle eine der folgenden:

  • 1. Make some file changes
    2. Commit them
    3. Stage them
    4. Push

  • 1. Make file changes
    2. Stage them
    3. Commit them
    4. Pull

  • 1. Make file changes
    2. Stage them
    3. Commit them
    4. Push

Erklärung

Frage 5 von 16

1

You created a branch from master and you have been working on it tirelessly. You have already made some changes but you havn't staged them.

Suddenly a colleague of yours says to you that he has updated the master branch on remote and you must downloaded the latest changes.

How are you going to save your file changes on your current branch without performing a commit, in order to fetch the new code from master?

Wähle eine der folgenden:

  • Git add --all

  • Git commit -m 'some changes'

  • Git push origin branch

  • Git stash

Erklärung

Frage 6 von 16

1

You have made a commit with some awesome changes and you pushed to remote. Unfortunately you have forgotten to add one small change to your previous commit. What should you do?

Wähle eine der folgenden:

  • After the changes, make a new commit, then push.

  • Fill the previous commit and add new changes there by typing *Git commit --amend*

Erklärung

Frage 7 von 16

1

A colleague of your has updated the master branch while you were working on your branch locally. You have already brought these changes to your local master and you want to have them to your local branch as well regardless of commit order.

What seems correct? Your branch's name is jake.

Wähle eine der folgenden:

  • 1. Git checkout master
    2. Git merge jake

  • 1. Git checkout jake
    2. Git merge master

  • 1. Git checkout master
    2. Git rebase jake

  • 1. Git checkout jake
    2. Git rebase master

Erklärung

Frage 8 von 16

1

When someone creates a local branch, that means that a corresponding branch is being automatically created on remote.

Wähle eins der folgenden:

  • WAHR
  • FALSCH

Erklärung

Frage 9 von 16

1

You have been working on your local branch and now you are ready to introduce these commits to your local master. What is the appropriate command given that you are standing on master now and given the name of your branch is jake.

Wähle eine der folgenden:

  • Git push jake

  • Git push origin master

  • Git merge origin master

  • Git merge jake

Erklärung

Frage 10 von 16

1

What is the appropriate action to get out of the merge process right after you have solved merge conflicts in text editor?

Wähle eine der folgenden:

  • 1. Git add --all
    2. Git commit -m 'some message about the merge'

  • 1. Git commit -m 'some message about the merge'

  • 1. Git stash
    2. Git commit -m 'some message about the merge'

  • Git push --force

Erklärung

Frage 11 von 16

1

What is the difference between merge and rebase?

Wähle eine der folgenden:

  • Rebase is a better option because you can pick a specific commit from another branch or from past and put it on top of your branch.

  • Rebase brings all commits from master branch and puts them on top of your branch's commits.

  • Rebase brings all commits from the specified branch but keeps the commits of your branch on top of them.

  • Rebase brings all the commits from the remote master but keep yours on top.

Erklärung

Frage 12 von 16

1

How do you discard changes that you accidentally made in a file that is currently unstaged? The file is example.scss
The commit that you are currently is eb4c29u.

Wähle eine der folgenden:

  • Git reset HEAD example.scss

  • Git revert HEAD

  • Git checkout eb4c29u

  • Git checkout -- example.scss

  • Git checkout example.scss

Erklärung

Frage 13 von 16

1

How to unstage a file that i have accidentally staged?

Wähle eine der folgenden:

  • Git checkout example.scss

  • Git reset --hard example.scss

  • Git reset HEAD example.scss

  • Git checkout HEAD

Erklärung

Frage 14 von 16

1

How can someone discard the last commit and return to previous one without deleting anything?
The commit hash is eb49uf2

Wähle eine der folgenden:

  • Git reset --hard eb49uf2

  • Git checkout eb49uf2

  • Git revert HEAD

  • Git cherry-pick eb49uf2

Erklärung

Frage 15 von 16

1

What is the appropriate action if someone wants to go back to the commit with hash eb49uf2 safely without deleting all the in-between commits?

Wähle eine der folgenden:

  • Git checkout eb49uf2

  • Git revert eb49uf2

  • Git merge eb49uf2

  • Git reset --hard eb49uf2

Erklärung

Frage 16 von 16

1

16. What does *Git cherry-pick* command do?

Wähle eine der folgenden:

  • To fetch all the code from a specific branch to your branch by putting the other branche's commits on top of your own.

  • To fetch all the code from a specific branch to your branch by putting your branche's commits on top of the others.

  • To bring a specific commit from different branch. This commit will go on top of your commits.

  • To bring a specific commit from different branch. This commit comes, but your branche's commits remain on top.

Erklärung

Vorherige
Nächste