You dense motherfuxker. There is a reason why we create a separate feature branch, put our code there, check the CI and THEN merge that to master. The whole reason of merge feature to master is that the CI DOES NOT GET FUCKED UP! You never keep committing your feature changes directly to master. THAT'S HOW YOU FUCK THE CI UP.

Who the fuck merges to master directly? Is there even a develop branch?!

@growling everyone works on development (feature) branch.... except this asshole who thought he is too cool for his own feature branch and kept pushing his development (feature) code to master .

I mean he should fucking check himself, but at my company we do the complete opposite. Everyone has their own branch they push to master. So maybe his history is making him think another way.

Can you not set up branch permissions to stop people from merging into master?

@jeeper yeah we have the same practice here. The guy joined along with me and we have the same industry experience. He has agreed to and fixed the CI but his constant babbling of "hey at least i fixed it, okay." is making me sick. Well I guess I am the stupid one who helped him with the fixes, explaining git strategies while merging and Jenkins jobs. You are fucking welcome!

@Badgerati We do have that. You need two approvals on your PR before merging. I have no idea how this guy managed to convince people to approve

Meanwhile some of my teammates use zip files over Gmail. Please kill me.

@varundey who approved should be the ones to help fix the shit ;)

Block pushing to master 🤣