Forking Workflow#

The forking workflow means that everyone on a team has permission to fork a repository and once they have completed their work, open a pull request to have it accepted into the main repository.

In a forking workflow, not everyone will have write access to the main repository. This means that only those with write access can merge pull requests once they have been approved. Usually, the forking workflow is used with Mercurial, and branching with Git.

Forking Overview#


Setting Up a Forking Workflow#

Setting up a forking workflow in RhodeCode Enterprise would look something like this.

  1. Create a user group with write access.

  2. Create a user group with read access.

  3. Assign team members to the appropriate groups.

  4. Users with contributions should open a pull request to the main repository and set a user with write access as the reviewer.

  5. Once the pull request is approved, the write access user would merge it with the main repository.

For more information about setting up user groups, see the User Administration section.

Using a Forking Workflow#

If you are on a team that uses a forking workflow, see the Forking and Branching section for how to fork a repository, and also the Pull Requests section.