[Other doc versions]
This page provides a high-level description of Git workflows that are supported by Stash. These come under two broad categories:
Branches in Stash provide for various workflows for developer teams. Some typical examples are described below. See Using branch permissions for more information about using branches in Stash.
If your developers are already comfortable with Subversion, the Centralized Workflow lets you experience the benefits of Git without having to adapt to an entirely new process. It also serves as a friendly transition into more Git-oriented workflows. Read more...
Feature branch workflow
The Feature Branch Workflow builds on the Centralized Workflow by encapsulating new features into dedicated branches. This enables the use of pull requests as a means to discuss changes before they’re integrated into the official project. Read more...
The Gitflow Workflow streamlines the release cycle by using isolated branches for feature development, release preparation, and maintenance. Its strict branching model also lends some much needed structure to larger projects. Read more...
Forks in Stash provide a workflow for developers to contribute code back to a repository for which they do not have write access. The merging of new code back into master may be controlled by a 'gatekeeper', and the review of code changes is performed by means of pull requests. Typical scenarios that suit fork workflows include:
See Using forks in Stash for more information.