Gonzako to Programmer Humor@programming.dev · 15 days agoBoys, don't dev alone or you'll end up with a git log like minevideomessage-square77linkfedilinkarrow-up1133arrow-down111
arrow-up1122arrow-down1videoBoys, don't dev alone or you'll end up with a git log like mineGonzako to Programmer Humor@programming.dev · 15 days agomessage-square77linkfedilink
minus-squareEvotechlinkfedilinkarrow-up3·14 days agoYea you always work on main on the same project. You don’t push broken code. You always need to keep mainline healthy It takes some special considerations, but the benefits are great.
minus-squarekewjolinkfedilinkarrow-up3·14 days agoso when something breaks both devs, the one who made the previous change and the person pushing new, have to work together to solve the issue? no PRs or is everything a fork? do you revert and rebase every change?
minus-squareEvotechlinkfedilinkarrow-up3·14 days agoYou revert the broken commit usually. https://martinfowler.com/articles/continuousIntegration.html This is a good article on the topic
minus-squareexu@feditown.comlinkfedilinkEnglisharrow-up2·14 days agoThat doesn’t stop you from removing your test commits before pushing
Yea you always work on main on the same project.
You don’t push broken code. You always need to keep mainline healthy
It takes some special considerations, but the benefits are great.
so when something breaks both devs, the one who made the previous change and the person pushing new, have to work together to solve the issue? no PRs or is everything a fork? do you revert and rebase every change?
You revert the broken commit usually.
https://martinfowler.com/articles/continuousIntegration.html
This is a good article on the topic
That doesn’t stop you from removing your test commits before pushing