VSTS | TFS 2018

Forks are a great way to isolate experimental, risky, or confidential changes from the original codebase. A fork is a complete copy of a repository, including all files, commits, and (optionally) branches. The new fork acts as if someone cloned the original repository, then pushed to a new, empty repository. After a fork has been created, new files, folders, and branches are not shared between the repositories unless a pull request carries them along. Once you're ready to share those changes, it's easy to use pull requests to push the changes back to the original repository.

The forking workflow

When working with forks, you typically use the following workflow:

  1. Create a fork
  2. Clone it locally
  3. Make your changes locally and push them to a branch
  4. Create and complete a PR to upstream
  5. Sync your fork to the latest from upstream

Learn more