-
Notifications
You must be signed in to change notification settings - Fork 0
/
git_05_WorkingWithRemoteRepositories.yaml
94 lines (93 loc) · 4.11 KB
/
git_05_WorkingWithRemoteRepositories.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
categoryId: 4719 # CATEGORY NAME
name: Working with remote repositories in Git
questions:
- description: What is a remote tracking branch?
choices:
- It is a branch of the remote repository
- It is a local reference to a branch of the remote repository
- It is a copy of the remote repository
-
hint:
explanation:
correctChoice: 1
- description: How do I get updates of remote-tracking branches?
choices:
- There is no way to get updates of remote-tracking branches
- Only the command git clone will can update them
- The command git fetch will do so
-
hint:
explanation:
correctChoice: 2
- description: Where can a remote repository be hosted?
choices:
- A remote repository is always hosted on a server
- A remote repository can be hosted on a server or in the local file system
- A remote repository can only be hosted in the local file system
-
hint:
explanation: It doesn't make a difference where the remote repository is hosted.
correctChoice: 1
- description: What is the difference btw. a remote repository and a remote?
choices:
- Remotes are shorter bookmarks for remote repositories
- There is no difference
- Remote is just a shorter name for remote repositories
-
hint:
explanation:
correctChoice: 0
- description: What is a bare repository?
choices:
- An empty repository without a commit
- A repository without a working tree to which other user can push their changes. It is typically hosted on a server
- A normal repository with a fancy name
- A repository with a working tree but with the option that other users can push their changes, it is typically hosted on a server
hint:
explanation:
correctChoice: 1
- description: What does the command git clone do?
choices:
- It copies only the latest version of the git repository without its previous history
- It creates a link to a git repository and updates the working tree with the latest changes from master
- It copies a git repository with its complete history, creates a link to the cloned repo named "origin" "and creates a local branch named master
- It creates a similiar version of a git repository
hint: Nothing ever gets lost with git.
explanation:
correctChoice: 2
- description: What happens if you delete a remote tracking branch in your local repostory?
choices:
- This is safe and does not affect a remote repository
- The branch will be deleted in the remote repository
-
-
hint:
explanation: After deleting a remote tracking branch it can be recreated with the 'git fetch' command
correctChoice: 0
- description: What happens if you delete a remote branch?
choices:
- This is safe and does not affect a remote repository
- The remote branch is completly deleted
- The git repository which includes the branch gets deleted
-
hint:
explanation:
correctChoice: 1
- description: Is a tracking branch automatically created by git?
choices:
- No, this is a manual process
- Yes, everytime you commit and push changes, git creates a tracking branch on the remote repository
- Yes, after cloning a repository or fetching the relevant remote branch information
-
hint:
explanation: If you clone a Git repository, your local master branch is created as a tracking branch for the master branch of the origin repository by Git.
correctChoice: 2
- description: Can multiple people work at the same remote repository?
choices:
- Yes, they can also push on the same branch as long as they only create a fast-forward merge on the server
- No, because of possible merge conflicts
- Yes, but every developer has to create their own branch
-
hint:
explanation: It is a common scenario that developers push to the same branch and typically, this branch evolves since the beginning of the development of a local feature and a push fails. But this situtation can be handled.
correctChoice: 0