[waffletower]

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]

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.

[NordSteve]

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.

[vlovich123]

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]

‘Works on my local’

[vlovich123]

No. Evergreen means CI tests your commit, not relying on individuals to be doing before pushing.

[arealaccount]

We used to have a git plugin that snaps a picture on every push, which accompanied the "alert". Was fun.

[0xffff2]

It's mind-blowing to me that any multi-user git repo is set up to allow pushes to main at all.

[waffletower]

It was years ago at a small outfit

[nicman23]

what a chad