2 ms·
Just use Gitflow peeps. It's simple, not mentally taxing, and having a feature branch for each feature (JIRA ticket, or whatever unit you're using) makes things
by sergiotapia 13y ago
Just use Gitflow peeps. It's simple, not mentally taxing, and having a feature branch for each feature (JIRA ticket, or whatever unit you're using) makes things very atomic and simple.
- sopooneo 13y agoAnd also, if new people join your team, they've probably at least heard of it. There is benefit to being in the middle of the pack.
- deleted 13y ago[deleted]
- ricardobeat 13y agoThis is simple and gives you one branch per feature. Gitflow doesnt offer any guidance on keeping a feature branch up-to-date, assuming either they are very short-lived (frequently untrue) or that you merge from develop polluting your history. In fact you can use this rebasing workflow within gitflow, both are good advice.