Workflow strategies in Bitbucket Server
Like Subversion, the Centralized Workflow uses a central repository to serve as the single point-of-entry for all changes to the project. Instead of
trunk, the default development branch can be customized and all changes are committed into this branch. This workflow doesn’t require any other branches besides the default branch.
Read more about the Centralized Workflow...
Feature Branch Workflow
The core idea behind the Feature Branch Workflow is that all feature development should take place in a dedicated branch instead of the default branch. This encapsulation makes it easy for multiple developers to work on a particular feature without disturbing the main codebase. It also means the default branch will never contain broken code, which is a huge advantage for continuous integration environments.
Read more about the Feature Branch Workflow...
The Gitflow Workflow defines a strict branching model designed around the project release. While somewhat more complicated than the Feature Branch Workflow, this provides a robust framework for managing larger projects.
Read more about the Gitflow Workflow...
The Forking Workflow is fundamentally different than the other workflows discussed in this tutorial. Instead of using a single server-side repository to act as the “central” codebase, it gives every developer a server-side repository. This means that each contributor has not one, but two Git repositories: a private local one and a public server-side one.
Read more about the Forking Workflow...