8

So I go on a 10day holiday and when I come back I realise the scrum master commited a whole bunch of messy code straight to develop and didn’t even bother to run lint or build or test or anything. WHYYYYY??? Everything worked before that. Why is a scrum master who doesn’t have experience in front end allowed to touch my code and commit directly to master?

I know why. Because the whole team does it all the time and they just keep breaking and fixing things over one another and all commit directly to master.

Kill me pleaseeeeeee 😭😭😭

Comments
  • 3
    You can leave... and let the world burn
  • 4
    I would take charge and say something like, "these commits are not authorized, syntactically compliant, or hygienically sound, so I'm rolling the repo back to where it was before them."
  • 1
    @bahua or that, that is fine too, and then lecture everyone on the team because wtf...
  • 0
    ive been asking them to add security to GitHub so not everyone can merge and commit and every time you commit to develop it would build the scripts and they said why don’t I trust them?? BITCH no I don’t trust you after what you did. I don’t trust any backend dev in my front end code just how you should not trust me on your backend code

    (Btw yes both front end and backend is the same repo)
  • 1
    @FastFwd00 It seems to be the perfect time to start reverting all the shit they do outside their scope.

    Backend developer, why you just edited this css or html? Revert! Why? Because you don't want me to mess with your controllers!
Add Comment