Developer creates pull request.

I hold suggesting changes.

Developer creates new branch and new pull request with exactly the same commit.

Another Senior developer approves pull request.

This will be discussed tomorrow morning!

Make them bleed

...and please report back here 📌

📌

.

Sock party!

Does anyone have extra popcorn? I forgot mine 😳

.

.

📍

At least give him credit for abusing Git clients in a clever way :D

📌

.

📌

This is going to be good!

..

📌

@jimmy213 there 🍿, I brought extra just in case.

I'm here for the tea

This one I can't miss.

💢

📍 🍿

This is interesting. Ive done that and seen people try to get around me.

📍

@gitpush Thanks 😀

📌

It's not quite at dramatic as you're all expecting but here's what happened.

I called a meeting to bring all the Devs in to talk about the issue, remind them of the reasons we have pull requests and the standards that we expect of them.

The Senior who approved the second one said he didn't realise the first request existed and didn't spot there were any issues. He clearly didn't review it properly but ok dealt with that.

The guy who caused this issue tried to justify it saying he needed to deliver the user story. I pointed out that is not the way we do delivery and highlighted the risks he was being to the project and the team. He accepted he was wrong.

@LMagnus always nice to have a good result. People make mistakes. Owning up to them is the key.

If only more people did that.

@Root I’ll grab the door knobs and bars of soap!