• xmunk@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    You already stopped Steven in a prior commit.

    Also, if this is an organization setting, I’m extremely disappointed in your PR review process. If someone is committing vendor code to the repo someone else should reject the pull.

  • xlash123@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    Correct me if I’m wrong, but it’s not enough to delete the files in the commit, unless you’re ok with Git tracking the large amount of data that was previously committed. Your git clones will be long, my friend

    • Backfire@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      You’d have to rewrite the history as to never having committed those files in the first place, yes.

      And then politely ask all your coworkers to reset their working environments to the “new” head of the branch, same as the old head but not quite.

      Chaos ensues. Sirens in the distance wailing.