Feature branches should have descriptive names, like animated-menu-items or issue-#1061. Instead of committing directly on their local main branch, developers create a new branch every time they start work on a new feature. The Feature Branch Workflow assumes a central repository, and main represents the official project history. The Gitflow, and Git Forking Workflows traditionally use a Git Feature Branch Workflow in regards to their branching models. The Git Feature Branch Workflow can be incorporated into other workflows. Git Feature Branch Workflow is branching model focused, meaning that it is a guiding framework for managing and creating branches.
We discussed other Git workflows on the Git workflow overview page. The Git Feature Branch Workflow is a composable workflow that can be leveraged by other high-level Git workflows. The point is, pull requests make it incredibly easy for your team to comment on each other’s work. Or, if you get stuck in the middle of a feature, you can open a pull request asking for suggestions from your colleagues. They give other developers the opportunity to sign off on a feature before it gets integrated into the official project. It also means the main branch will never contain broken code, which is a huge advantage for continuous integration environments.Įncapsulating feature development also makes it possible to leverage pull requests, which are a way to initiate discussions around a branch. This encapsulation makes it easy for multiple developers to work on a particular feature without disturbing the main codebase. The core idea behind the Feature Branch Workflow is that all feature development should take place in a dedicated branch instead of the main branch.
0 kommentar(er)
