SagXD to Programmer Humor@programming.dev • 7 days agoCoomitter be likelemm.eeimagemessage-square44fedilinkarrow-up1432arrow-down121
arrow-up1411arrow-down1imageCoomitter be likelemm.eeSagXD to Programmer Humor@programming.dev • 7 days agomessage-square44fedilink
minus-squareDacoTacolinkfedilink4•edit-27 days agoSame haha. But i use a combination of commits ( but not pushed ), ammending, fixups and usually clean it up before making a PR or pushing ( and rebase/merge main branch while at it). Its how git should be used…
minus-square@RustyNova@lemmy.worldlinkfedilink5•7 days agoI do push often as I’m often switching between two devices. And I do make draft PR so I got an easy git diff that I can live reference with
minus-square@verstra@programming.devlinkfedilink3•7 days agoYou are not alone. This is the work git was built for. There is a bit of benefit if you have code reviewed so separate commits are easier to review instaed of one -900 +1278 commit.
Same haha. But i use a combination of commits ( but not pushed ), ammending, fixups and usually clean it up before making a PR or pushing ( and rebase/merge main branch while at it). Its how git should be used…
I do push often as I’m often switching between two devices. And I do make draft PR so I got an easy git diff that I can live reference with
You are not alone. This is the work git was built for.
There is a bit of benefit if you have code reviewed so separate commits are easier to review instaed of one -900 +1278 commit.