Git FEATURE branch WorkFlow

• Core Idea
  • all feature development should take place in a dedicated branch instead of the main branch
  • Advantage? Multiple devs work in parallel on multiple features without disturbing the main branch
  • the main branch will never contain broken code, which is a huge advantage for continuous integration environments.
• pull requests make it incredibly easy for your team to comment on each other’s work.
• Working
  • The Feature Branch Workflow assumes a central repository, and main represents the official project history
  • Instead of committing directly on their local main branch, developers create a new branch every time they start work on a new feature.
  • Feature branch names should be clear, concise and carry meaning - descriptive names
  • Feature branches should be pushed to main(central) repository,
    • code gets shared to other devs
    • Main working code base is not touched! (Win Win)
  • workflows are designed to be guidelines rather than concrete rules
• Code review is a major benefit of pull requests, but they’re actually designed to be a generic way to talk about code.

• You can think of pull requests as a discussion dedicated to a particular branch

• This workflow helps organize and track branches that are focused on business domain feature sets.