When an open source contribution appeared from someone new, I used to feel excitement.

context: https://mstdn.social/@dazfuller/116080728819432902

@mossmann Once you morge continvoucly you never go back!

RE: https://mastodon.social/@mossmann/116086520011187648

@mossmann Morges is indeed quite lovely, and worth continvoucling.

https://en.wikipedia.org/wiki/Morges

@mossmann https://l5r.fandom.com/wiki/Morge

King of the Trolls!

@mossmann practice safe code, morge intern

@mossmann an important aspect of this is figuring out how to Timm backwards. If you can’t do that then you can’t possibly hope to morge anything.

@kemotep @mossmann I've seen this diagram a few times, but I just realized that I think "tim" is supposed to be "time". What a wild trip.

@mossmann It's morgin tim(e)?

@mossmann mighty morging PR rangers

@mossmann this Morg Approved

@scottmiller42 @mossmann it’s actually like a triple m or something weird. I don’t think there is a UTF character to actually match it in text lol

@mossmann code review after merge is a valid strategy

see https://martinfowler.com/articles/ship-show-ask.html

@mossmann in fact the merge request workflow was later added and git itself works without it (git patch, anyone?). Some people e. g. Martin Fowler say the concept of a merge request is antithetical to the concept of CI. You can't have these unmerged branches and pretend you do CI (many don't know this)

@mossmann When you morge, you push to prud

@mossmann moooorrrgeee!

@mossmann

^^ regert

@mossmann @billgoats my favorite part is when he says “it’s morgin’ time” and then morges all over them