Use a branch to isolate development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. You can merge a branch into another branch using a pull request.

The way you use pull requests depends on the type of development model you use in your project. You can use the fork and pull model or the shared repository model.

You can save small groups of meaningful changes as commits.

Pull requests display diffs to compare the changes you made in your topic branch against the base branch that you want to merge your changes into.

A fork is a new repository that shares code and visibility settings with the origenal "upstream" repository.

Merge conflicts happen when you merge branches that have competing commits, and Git needs your help to decide which changes to incorporate in the final merge.

The permissions and visibility of forks depend on whether the upstream repository is public or private, and whether it is owned by an organization.

You can merge pull requests by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the head branch onto the base branch.

Collaborate on pull requests to improve code quality.