▲ 267 ▼ Let's blame the dev who pressed "Deploy" (yieldcode.blog) submitted 2 years ago by Brkdncr@lemmy.world to c/technology@lemmy.world 68 comments fedilink hide all child comments
[+] 0x0@programming.dev -10 points 2 years ago (2 children) Oh you sweet summer child... permalink fedilink source parent hideshow 4 child comments replies: [–] erwan@lemmy.ml 11 points 2 years ago I hate to break it to you, but companies with actual safe rails to deploying to production do exist. And when things go wrong, it's never the responsibility on a single dev. It's also the dev who reviewed the PR. It's also the dev who buddy approved the deploy. It's the whole department that didn't have enough coverage in CI. permalink fedilink source parent [–] aodhsishaj@lemmy.world 10 points 2 years ago I would hate to work where you developed the idea a protected main/prod branch is something novel. permalink fedilink source parent
[–] erwan@lemmy.ml 11 points 2 years ago I hate to break it to you, but companies with actual safe rails to deploying to production do exist. And when things go wrong, it's never the responsibility on a single dev. It's also the dev who reviewed the PR. It's also the dev who buddy approved the deploy. It's the whole department that didn't have enough coverage in CI. permalink fedilink source parent
[–] aodhsishaj@lemmy.world 10 points 2 years ago I would hate to work where you developed the idea a protected main/prod branch is something novel. permalink fedilink source parent