The only benefit that I see here is that I don't end up accidentally pushing to master, which has happened to many projects that I have worked on in the past.
Cofounded Host Collective (DiscountASP.net). Cofounded Player Axis (Social Gaming). Computer Scientist and Technology Evangelist with 20+ years of experience with JavaScript!
The 2nd method to create a feature branch described will never run into merge conflict.
Another benefit is that you do not need to enter (checkout) the master branch to create a new feature branch. The feature can be created from anywhere.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The only benefit that I see here is that I don't end up accidentally pushing to master, which has happened to many projects that I have worked on in the past.
One benefit is that you would not need to perform a merge. Any time you do
git pull
, you run the risk of having merge conflicts and having to merge.New Branch with master
New Branch without master
The 2nd method to create a feature branch described will never run into merge conflict.
Another benefit is that you do not need to enter (
checkout
) the master branch to create a new feature branch. The feature can be created from anywhere.