This question already has an answer here:

Using multiple branch/developers strategy for developing features causes some issues with built-in Drupal configuration management.

Our scenario is the following:

  1. Create new feature and export config using drush
  2. Commit changes and configuration into git
  3. Move to another branch and start working in another feature
  4. Export config using drush (also exports config from the features added in the previous branch)
  5. Cannot move easily between branches as some content types are missing

What is the best way to use feature branches in a multiple developer team without creating this overhead?

marked as duplicate by Pierre.Vriens, DRUPWAY, Clive Feb 21 '17 at 9:39

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Can you add some details about how does this question differs from this question? – Pierre.Vriens Feb 21 '17 at 9:26
  • That question is about the features module; this question doesn't mention the features module, just feature branches – Clive Feb 21 '17 at 10:48