Always commit

Comments

• chickenf622@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  He doesn’t want to push at such a late hour. Give him a break.

  source

  • superduperenigma@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Gotta have something to say in stand-up the next morning, otherwise your PM will assign you another task.

    source
  • eestileib@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    How many times did I push at 2am so I could go home, get to the freeway entrance, realized I fucked something up, sighed, and turned around to go back and fix it…

    (This was like 1999, we didn’t have access to Perforce from home).

    After a year or so I realized I should just develop the willpower to check it in after sleeping on it.

    source

    • jaybone@lemmy.world ⁨1⁩ ⁨year⁩ ago

      Oh god Perforce.

      source

      • -> View More Comments
• yiliu@informis.land ⁨1⁩ ⁨year⁩ ago

  “No, wait, it’s not what you think! There’s a continuous integration system, a commit would’ve triggered a new build! It might have paged the oncall! Babe! The test suite has been flaky lately!”

  source
• Cqrd@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

  Dude just stopped before he got to a logical stopping point where it would make sense to commit and push

  source

  • GigglyBobble@kbin.social ⁨1⁩ ⁨year⁩ ago

    That's actually not the rare when I work later than usual. Some stupid problem my brain is too fried to solve. Eventually I give up, feeling defeat for the whole evening and solve the problem in 10 mins the next morning. Get enough sleep, people.

    source
• min_fapper@iusearchlinux.fyi ⁨1⁩ ⁨year⁩ ago

  The most common advice for git is

  commit early. commit often

  Do not however, follow the same advice for relationships.

  source
• ______@lemm.ee ⁨1⁩ ⁨year⁩ ago

  I worked today and have O commits.

  source
• devious@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Well maybe if she had shown more interest in his pull requests, he wouldn’t be off forking other repos!

  source
• Zeth0s@lemmy.world ⁨1⁩ ⁨year⁩ ago

  I never push as last thing in the evening. I want to sleep and revise it in the morning. --amend crew unite

  source

  • Michal@programming.dev ⁨1⁩ ⁨year⁩ ago

    What if while you sleep over it your laptop gets stolen or damaged? I’d rather push every small change than sit on it.

    source

    • Zeth0s@lemmy.world ⁨1⁩ ⁨year⁩ ago

      I would lose max 3 hrs of work that I already know how to re do. I can live with that. I don’t want to publish unfinished work. There is always the chance someone might need the branch.

      source

      • -> View More Comments
    • darklamer@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

      Don’t you have continuous backups of your work laptop!?

      source

      • -> View More Comments
• gitstash@lemmy.world ⁨1⁩ ⁨year⁩ ago

  git stash, girl

  source
• cupcakezealot@lemmy.blahaj.zone ⁨1⁩ ⁨year⁩ ago

  never commit on friday afternoon because you’ll regret it on monday morning

  source
• HubertManne@kbin.social ⁨1⁩ ⁨year⁩ ago

  commit history was how I determined when to do the nightly and big weekend backups for a place I admined at one point. It was so annoying that we had one developer that liked to stay up way late and one that like to get up way the fuck early. Thank god they were all colocated at that point in time. If they had different timezones I would have just had to say eff it and let them have some poorer preformance.

  source
• atticus88th@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Honey, I was reviewing the new interns pull request. She was having a real hard time. We kept pushing and pulling until we eventually found ourselves getting that commit all over the codebase. Needless to say it won’t happen again, it was a one night standing review.

  source