GitHub MLSA

What is the best way to report a bug to a GitHub project?

• Send an email to a project owner.

• I don't bother reporting software bugs because there's no transparency and they never get fixed anyway.

• Search for the bug in the project's existing issues and create a new one if it hasn't been reported yet.

Answer explanation

A project's issues are visible to anyone who has access to the project, so you may find a resolution is already planned or available. Otherwise, you can create and track the issue yourself.

Suppose you have created a bug fix on a new branch and want it to become part of the next production build generated from the main branch. What should you do next?

• Copy your branch changes and commit them directly to the main branch.

• Create a pull request to merge your new branch into the main branch.

• On second thought, maybe I won't share this fix. I'll just put it in my own private version of the source code.

Answer explanation

Pull requests are the correct way to communicate that commits are ready for review and ultimate inclusion on the main branch.

Suppose you'd like to work with a project on GitHub but you don't have write access to the project. What can you do to contribute?

• Fork the project's repository to your GitHub account, clone the forked repository to your local machine, push changes to your repository, and submit a pull request to the target (upstream) repository.

• Clone the project to your local machine and push updates directly to the project repository.

• Use git commands to make a copy of the project so that you can work locally. Submit an issue to get your changes into the target repository.

Answer explanation

GitHub provides forking functionality designed to allow you to work with projects where you aren't an owner or don't have write access. Forking makes a remote copy of the project in your repository that you can then clone locally. To submit updates to the target repository (upstream repository) you can submit a pull request.

What’s the difference between Git and GitHub?

• Git lets you work with one or more local branches and push changes to a remote repository. GitHub acts as the remote repository, which is accessed through a website or command-line tools.

• Git is a distributed version control system (DVCS) that runs in the cloud. GitHub is an interface layer that provides access to Git technology.

• Git is used by an individual contributor. GitHub is used by multiple contributors to simplify group development work.

Answer explanation

Correct! Git is the tool you can use to work with a local branch and push changes to a remote repository. GitHub acts as the remote repository.

Which of the following statements is true about branches in Git?

• Work done on a branch doesn't interfere with work in other branches.

• A branch can't have any other branches that extend from its line of development.

• The default branch in a Git repo is named master and this branch name can never be changed.

Answer explanation

Correct!

The purpose of branches is to isolate changes in one branch from changes made in another branch, until you're ready to merge the changes in both branches together.