3 ms·
Gonna be honest with y'all. You don't need a git workflow. Seriously, YAGNI. Deploy every `master`, no other restrictions. Git workflows are over-engineering.
by renewiltord 6y ago
Gonna be honest with y'all. You don't need a git workflow. Seriously, YAGNI. Deploy every `master`, no other restrictions.
Git workflows are over-engineering.
- AlphaSite 6y agoThat works if you have a deploy step. There’s a world beyond SAAS. A very lucrative one.
- renewiltord 6y agoOh that's entirely fair. I was 100% thinking SaaS because of the website we're on, but if you do have to maintain multiple versions for whatever reason, you're going to need a complex flow with multiple trunks.
- kingosticks 6y agoI don't see how SaaS is immune to this. You could easily find yourself with a big customer that effectively wants their own deployment and doesn't want updates (new bugs / big changes) but still demands occasional fixes/features that you often want to also merge into the main deployment.
- renewiltord 6y agoIt's not immune since few things in life have a measure zero or measure one probability. It is unlikely, though, imho.
- steve_taylor 6y agoThe key is to avoid having customers so big you can’t afford to lose them.