last week i got to witness an engineering department lose a full day's work because if you put an emoji in a git commit message, Atlassian Bamboo chokes on it forever and you're forced to rebase master, like you should NEVER DO. this was of course referred to as The Emojiency
-
Show this thread
-
-
Replying to @RyanAlban1
Chaos Retweeted Joseph Schiarizzi
well, for examplehttps://twitter.com/CupOJoseph/status/1119785603342708736 …
Chaos added,
1 reply 0 retweets 1 like -
Replying to @chaosprime
But... why? In 10 years, someone crawling the history without that guide will have no idea what's going on. The facepalm mentioned in other threads seems like a slippery slope to value judgments being in commit logs, which is a bit unprofessional. So... Why do we need this?
3 replies 0 retweets 4 likes -
Replying to @RyanAlban1
Chaos Retweeted Chaos
i mean, it was absolutely a value judgmenthttps://twitter.com/chaosprime/status/1119981032424529920 …
Chaos added,
1 reply 1 retweet 0 likes -
Replying to @chaosprime @RyanAlban1
i don't care whether it's considered that we "need" it, if we shouldn't have it, allowing it then having tools shit themselves on it later is not the correct implementation
1 reply 0 retweets 21 likes -
Replying to @chaosprime
Indeed, I agree with you there. I just find it concerning that this edge case is being hit in the first place.
2 replies 0 retweets 3 likes
sure. well, clearly your values are being largely adhered to if this organization has been using git and Bamboo for years and only just now found this out
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
can't see how that could have been improved upon