• Otter@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    6 days ago
    rm -rf *
    
    git add -A
    git commit -m "oops."
    
    rm -rf .git
    git init
    git add .
    git commit -m "bye."
    
    git push origin main --force
    
      • Otter@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        6 days ago

        Oh good point 🤦

        So maybe instead, we can clear all local + remote branches and tags, create a blank branch, delete main, rename the blank branch to main, then delete .git

        Although the OP says that we can merge anything, and we might not have access to mess with branches

    • Miaou@jlai.lu
      link
      fedilink
      arrow-up
      0
      ·
      6 days ago

      Wdym you don’t like waiting 3 weeks for a code owner to approve a 1 line change?

  • red_tomato@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    6 days ago

    Another movie pitch:

    Due to management decision, a code freeze has been mandated to the main branch. 50 feature branches have accumulated waiting to be merged.

    Management has now finally approved to lift the code freeze - but only for 24 hours. Will the poor engineering team manage to merge all feature branches in time?

    • Jesus_666@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      6 days ago

      Here’s one for a TV show.

      In 2022, a crack quality assurance team was made redundant by a CTO for a botched product launch they didn’t commit.

      These men promptly escaped from a maximally unstable job market to the LinkedIn underground.

      Today, still wanted by recruiters, they survive as soldiers of fortune.

      If you have a broken codebase, if no one else can help, and if you can find them, maybe you can hire the QA-team.