Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We commit everything to master and run CI/CD(staging) on every remote push.

If some work isn't release-ready by EOD it's pushed to a branch overnight so it's not just on a single laptop.

That's it. Works great!



Yes. Horses for courses, but in every case that I have seen, mostly web apps, merge to master is what works best. And things like long-lived branches, complex strategies and gitflow are a waste of time, counterproductive, or even actively harmful.

Also it's worth noting that unless you don't have a "shared mainline" (i.e. master branch) that all dev changes are merged to, frequently; then you can't have Continuous Integration

https://en.wikipedia.org/wiki/Continuous_integration




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: