Module: Git and GitHub Basics “Answers”

I)Overwriting changes made by other users
II)Corruption of shared file servers
III)Deployment failures
IV)Merge conflicts
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
I)Overwriting changes made by other users
[/bg_collapse]

I)Maintaining regular backups of team member’s laptops
II)Enforcing strict rules and processes on team members
III)Provides a one-size-fits-all solution for teams to collaborate
IV)Provides a way to organize work from many team members
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)Provides a way to organize work from many team members
[/bg_collapse]

I)Git is a VCS. GitHub is a collaboration platform that is built on top of Git.
II)GitHub is Git for teams.
III)Git and GitHub are the same product, but with slightly different names based on whether you use it locally or through a web browser.
IV)GitHub is the graphical user interface for Git, but it has identical functionality.
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
I)Git is a VCS. GitHub is a collaboration platform that is built on top of Git.
[/bg_collapse]

I)A shared drive for maintaining backups of project versions
II)A Flash drive for sharing files with team members
III)Continuous integration
IV)A backup strategy for compiled versions of your project
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)Continuous integration
[/bg_collapse]

I)Code tab
II)Issues tab
III)Pull Requests tab
IV)Projects tab
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
I)Code tab
[/bg_collapse]

I)Individual
II)Organization
III)Team
IV)Administrator
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
II)Organization
[/bg_collapse]

I)Merging
II)Committing
III)Branching
IV)Cloning
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)Branching
[/bg_collapse]

I)git pull
II)git merge
III)git status
IV)git commit
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
I)git pull
[/bg_collapse]

I)It doesn’t matter.
II)Shorter is better all the time.
III)Shorter is best, but long-lived branches may be appropriate in some cases.
IV)Long-living branches are better for small teams.
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)Shorter is best, but long-lived branches may be appropriate in some cases.
[/bg_collapse]

I)About 2 hours’ worth of work
II)All of the changes necessary to implement the requested feature
III)A single line of code
IV)Enough for a small, logical unit of change
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
IV)Enough for a small, logical unit of change
[/bg_collapse]

I)git reset –soft
II)git commit –amend
III)git revert
IV)git rebase
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)git revert
[/bg_collapse]

I)A rebase is the same as a merge.
II)A rebase lets you move from a fast-forward to a recursive merge scenario.
III)A rebase enables you to move from a recursive to a fast-forward merge scenario.
IV)A rebase lets you select the merge strategy you would like to use.
[bg_collapse view=”button-orange” color=”#4a4949″ expand_text=”Show Answers” collapse_text=”Close Answer” ]
III)A rebase enables you to move from a recursive to a fast-forward merge scenario.
[/bg_collapse]