4 ms·
The idea is you never push your feature branches, they exist on your machine only - same as the stash. If you are concerned about force push then make sure peo
by seabee 12y ago
The idea is you never push your feature branches, they exist on your machine only - same as the stash.
If you are concerned about force push then make sure people understand the workflow and/or enforce branch creation policies on your central repo.
- cjantz 12y agoIf you take it like that you can also say ignore the squash and keep the merge commit clean. That way you don't push all your development commits to the remote and ensure a clean streamlined history. A problem some teams I worked with have is that there is not one person working on a feature. Especially if you have feature-driven development teams at least 2-3 people actually work on it and a review process is included. That's why teams need to push their feature branches to the remote. Once they are merged: Feel free to delete them. But in my opinion it's hard to work on one feature with several people without distributing the feature branch.