for example , my project have two branches, master and test.Branch master is used for code which is already tested and can be delivered, Branch test is used for code which is just submitted and need to be tested.But Since we have 5 developers and we want to create 5 sub branches in test branch , what can I do?
how to create multi-level remote branch in git?
1.2k Views Asked by wuchang At
1
There are 1 best solutions below
Related Questions in GIT
- How to set a component published attribute
- using dart route package url got error 404
- Using Document Discovery service on a non-app engine service
- Setting height of bwu-datagrid to dynamic
- use sass transformer in intellij dart
- Get 3D cube from an Obb3
- Send event from parent to child element in polymer.dart
- In the dart:io library, why would one want to set runInShell: true when calling Process.run?
- Can two @published properties have the same name
- dartanalyzer doesn't give a warning for missing implementation from interface
Related Questions in GIT-BRANCH
- How to set a component published attribute
- using dart route package url got error 404
- Using Document Discovery service on a non-app engine service
- Setting height of bwu-datagrid to dynamic
- use sass transformer in intellij dart
- Get 3D cube from an Obb3
- Send event from parent to child element in polymer.dart
- In the dart:io library, why would one want to set runInShell: true when calling Process.run?
- Can two @published properties have the same name
- dartanalyzer doesn't give a warning for missing implementation from interface
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
If ever you want more branches, simply create them. Pick a good spot to base them from (some commit on master would be ideal), and you and your team can work from there.
In a few Git workflows - notably Git Flow - this strategy comes to be known as creating feature branches; that is, a branch for a feature which is relatively short lived, merged into an integration branch for testing, and merged into production code. Since branches are inexpensive to create, it would be a good idea to create a branch per feature, merge it into your test branch, and once it's ready to go, merge it from the test branch into master and delete the feature branch.
I would not advise that you create a branch per developer, as this means that the work they're doing quickly becomes conflated with the branch they're on. More granular changes mean that integration points are a lot less painful when the time comes to merge everything upstream.