SagXD@lemm.ee to Programmer Humor@programming.dev · 4 months agoCoomitter be likelemm.eeimagemessage-square41fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageCoomitter be likelemm.eeSagXD@lemm.ee to Programmer Humor@programming.dev · 4 months agomessage-square41fedilink
minus-squareDacoTaco@lemmy.worldlinkfedilinkarrow-up0·edit-24 months 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-squareverstra@programming.devlinkfedilinkarrow-up0·4 months 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.
minus-squareRustyNova@lemmy.worldlinkfedilinkarrow-up0·4 months 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
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…
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.
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