top 50 comments

sorted by: hot top controversial new old
[–] 99 points 2 years ago (1 child)

Me burning to death fixing pylint warnings before I can commit my code.

  • source
  • hideshow 2 child comments
  • [–] 76 points 2 years ago* (last edited 2 years ago) (4 children)

    Why is the wrong version always the one that is posted.

    The (in my eyes) correct (and iirc original) version is:

    • Git commit
    • Git push
    • Get out*

    *as someone pointed out (and I remember it as well, but thought I rembered it wrong and corrected it, shame on me in this context) the last point may be originally "git out"

  • source
  • hideshow 7 child comments
  • load more comments (1 reply)
    [–] 56 points 2 years ago (3 children)
  • [–] 21 points 2 years ago

    Here at Company Inc, we continue to send our thoughts and prayers to the 38 interns who perished in the office fire of '07. Sixteen years later, we still mourn the loss caused by this unpredictable, unpreventable, and unlitigatable accident. We hope that, in time, the grieving families of those interns are eventually able to move on with both their hearts and their loved ones' funeral expense debts.

  • source
  • parent
  • [–] 6 points 2 years ago (1 child)

    On a push? What are you merging there?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (1 child)

    Ofc, you might be working directly on develop/master/shared branch, I know people that work in those environments (ew)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 years ago

    Right, on shared branch you might need to pull first if you're out of date (and you would be if you're all leaving the office at the same time), and that could cause a merge conflict.

    It's like I always said, bad branching strategies are a fire safety issue.

  • source
  • parent
  • [–] 48 points 2 years ago* (2 children)

    i read a reddit post years ago where a someone wrote a script that iterates through all the projects in their dev folder, for each project creating a new branch, committing and pushing.

    they then aliased it to "fire" or "panic" or something like that.

    not a bad idea really

  • source
  • hideshow 4 child comments
  • [–] 10 points 2 years ago (1 child)

    As in one they'd manually run if there was a fire?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 2 years ago (1 child)

    Exactly. The alias just points to the script which is executed.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 37 points 2 years ago (10 children)

    Slight correction. In case of fire:

    Git checkout -b firemyusername Git commit -am="fire" Git push.

    We don't want to have conflicts with code versions when going in on a rush, better to create a new branch. We can merge all the conflicts afterwards.

  • source
  • hideshow 10 child comments
  • load more comments (10 replies)
    [–] 35 points 2 years ago (1 child)

    Cause of death: 15 minute long pre-push hook

  • source
  • hideshow 2 child comments
  • [–] 29 points 2 years ago

    In case of

    Git commit

    Git push origin main --force

    Fire

  • source
  • [–] 26 points 2 years ago (1 child)
  • [–] 25 points 2 years ago* (1 child)
    load more comments (1 reply)
    [–] 22 points 2 years ago (2 children)
  • load more comments (1 reply)
    [–] 13 points 2 years ago* (1 child)

    Counterpoint: Virtualized environment/remote desktop. The real computer is in a data center hundreds of kilometers away with world class fire suppression systems.

    Counter counterpoint: If you're virtualized you might be working from home, in which case, that's rough, hope they manage to restore your house.

  • source
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (1 child)

    With a laggy desktop experience i also can't really configure how i want? No thank you. It's bad enough i have to use Windows for software development instead of letting me install Linux

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago* (1 child)

    I like it because I don't have any of the company's shit on my own machine. I absolutely don't trust them not to spy on my personal computer use if they had access to it. With remote desktop I close it at the end of the work say and it has no more access to my computer than I have access to their critical systems.

    In my case, their shit that we're required to use don't even support Linux so if it wasn't for virtualized environment I'd had to install Windows on my own machine.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
  • [–] 13 points 2 years ago

    Mark this shit NSFW. I could have viewed it at work.

  • source
  • [–] 9 points 2 years ago

    And if your git repo is self-hosted on-prem, you'd better be helping pack it and carry it out.

  • source
  • [–] 9 points 2 years ago (1 child)

    no changes added to commit (use "git add" and/or "git commit -a")

  • source
  • hideshow 2 child comments
  • [–] 3 points 2 years ago* (last edited 2 years ago) (1 child)

    It should (at least) be:

    git commit -a -m "🚨🔥🚨"
    git push --force
    

    Better, create a new branch and push it to origin(?).

    Relevant The IT Crowd

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 years ago*

    I've got something similar on my office door that reads

    In case of fire git commit -a git push git -tf out

  • source
  • [–] 6 points 2 years ago

    First, git checkout -b omgFire, then do the rest.

  • source
  • [–] 6 points 2 years ago

    This is a lawsuit waiting to happen. Anyway any of you ever heard of ACID? Why aren't our undo buffers durable and integrated with version control? Squash and forget the individual keystrokes as soon as an actual commit is made.

  • source
  • [–] 3 points 2 years ago (1 child)

    If the flames are nearby I would be so reckless and execute git push --force.
    I don't want to die for a merge conflict.
    But maybe then the team will burn me later.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 3 points 2 years ago

    Sorry to be that guy but I don't think it's smart to put this anywhere in public, keep this shit somewhere private as a joke

  • source
  • [–] 3 points 2 years ago

    Commit message: It's lit🔥🔥🔥

  • source
  • load more comments
    view more: next ›