3 ms·
I still cannot get my head round the fact that people don't know about TBD, and that there are substantial numbers of people not doing it. It's how all source
by twic 6y ago
I still cannot get my head round the fact that people don't know about TBD, and that there are substantial numbers of people not doing it.
It's how all source control was done before DVCS. It's pretty much the default workflow with a DVCS - if you read the Git docs and do the simplest things, you're doing TBD! It works perfectly well for most people.
How do people get to the situation where they know about Git Flow, but don't know about TBD? This feels like a huge failure of education or documentation or something.
- pseudalopex 6y agoTrunk based development isn't how all source control was done before DVCS.[1] The Git documentation suggests using long running branches.[2] "A successful Git branching model" was very influential. Git Flow sounds official. GitHub Flow sounds like Git Flow. [1] https://trunkbaseddevelopment.com/alternative-branching-models/index.html#mainline https://trunkbaseddevelopment.com/alternative-branching-mode... [2] https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows https://git-scm.com/book/en/v2/Git-Branching-Branching-Workf...