Gonzako@lemmy.world to Programmer Humor@programming.dev · edit-23日前Boys, don't dev alone or you'll end up with a git log like minelemmy.worldvideomessage-square78fedilinkarrow-up1123
arrow-up1123videoBoys, don't dev alone or you'll end up with a git log like minelemmy.worldGonzako@lemmy.world to Programmer Humor@programming.dev · edit-23日前message-square78fedilink
minus-squareEvotech@lemmy.worldlinkfedilinkarrow-up2·edit-23日前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.
minus-squareexu@feditown.comlinkfedilinkEnglisharrow-up1·2日前That doesn’t stop you from removing your test commits before pushing
minus-squarekewjo@lemmy.worldlinkfedilinkarrow-up1·3日前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?
minus-squareEvotech@lemmy.worldlinkfedilinkarrow-up2·edit-23日前You revert the broken commit usually. https://martinfowler.com/articles/continuousIntegration.html This is a good article on the topic
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.
That doesn’t stop you from removing your test commits before pushing
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