4 ms·

Reminds me of a colleague back in the day who would force push to main and just leave a "YOLO" comment in the commit.

• shepardrtc 1y ago
  At my last job, whenever a commit wouldn't build, we would blast it into a slack channel with an alert that included the comment and the name of the developer.
  • vlovich123 1y ago
    Ah yes. Public shaming. The “beatings will continue until morale improves” strategy of code development. Next time, you may want to suggest an evergreen strategy where commits are tested before they’re merged.
    • baq 1y ago
      ‘Works on my local’
      • vlovich123 1y ago
        No. Evergreen means CI tests your commit, not relying on individuals to be doing before pushing.
  • NordSteve 1y ago
    At one job, we had a garish chicken hat that lived in your office if you were the last one to break the build. This was in the days before automated CI, so a broken commit meant that someone wasn't running the required tests.
  • arealaccount 1y ago
    We used to have a git plugin that snaps a picture on every push, which accompanied the "alert". Was fun.
• 0xffff2 1y ago
  It's mind-blowing to me that any multi-user git repo is set up to allow pushes to main at all.
  • deleted 1y ago
    [deleted]
  • waffletower 1y ago
    It was years ago at a small outfit
• nicman23 1y ago
  what a chad