0
0
Gitdevops~10 mins

Distributed vs centralized version control in Git - Interactive Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the command to clone a remote Git repository to your local machine.

Git
git [1] https://github.com/user/repo.git
Drag options to blanks, or click blank then click option'
Aclone
Bmerge
Cpush
Dcommit
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'commit' instead of 'clone'
Using 'push' which sends changes, not copies repo
2fill in blank
medium

Complete the command to send your local commits to the remote repository.

Git
git [1] origin main
Drag options to blanks, or click blank then click option'
Apush
Bfetch
Cclone
Dpull
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'fetch' or 'pull' which only download changes
Using 'clone' which copies repo
3fill in blank
hard

Complete the command to update your local repository with changes from remote.

Git
git [1] origin main
Drag options to blanks, or click blank then click option'
Acommit
Bpull
Cclone
Dpush
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'push' instead of 'pull'
Using 'clone' which copies repo instead of updating
4fill in blank
hard

Fill both blanks to create a new branch and switch to it in Git.

Git
git [1] -b [2]
Drag options to blanks, or click blank then click option'
Acheckout
Bmain
Cfeature
Dcommit
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'commit' instead of 'checkout'
Using 'main' as new branch name when 'feature' is intended
5fill in blank
hard

Fill all three blanks to push commits and set the upstream tracking branch, enabling easy future syncs in distributed Git.

Git
git [1] --set-upstream [2] [3]
Drag options to blanks, or click blank then click option'
Apush
Borigin
Cmain
Dpull
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'pull' which fetches instead of pushes
Wrong remote/branch or omitting '--set-upstream'