Gonzako@lemmy.world to Programmer Humor@programming.dev · edit-2il y a 6 joursBoys, don't dev alone or you'll end up with a git log like minelemmy.worldvideomessage-square78fedilinkarrow-up1122
arrow-up1122videoBoys, don't dev alone or you'll end up with a git log like minelemmy.worldGonzako@lemmy.world to Programmer Humor@programming.dev · edit-2il y a 6 joursmessage-square78fedilink
minus-squareEvotech@lemmy.worldlinkfedilinkarrow-up3·edit-2il y a 5 joursYea 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-squarekewjo@lemmy.worldlinkfedilinkarrow-up2·il y a 5 joursso 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-squareEvotech@lemmy.worldlinkfedilinkarrow-up3·edit-2il y a 5 joursYou revert the broken commit usually. https://martinfowler.com/articles/continuousIntegration.html This is a good article on the topic
minus-squareexu@feditown.comlinkfedilinkEnglisharrow-up1·il y a 5 joursThat 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