3 ms·
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.
by 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 agoAh 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 agoNo. Evergreen means CI tests your commit, not relying on individuals to be doing before pushing.
- NordSteve 1y agoAt 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 agoWe used to have a git plugin that snaps a picture on every push, which accompanied the "alert". Was fun.