5 ms·
For git commit messages. I've began liking to initiate or end a statement with stuff like these: ¯\_(ツ)_/¯ ( ͡° ͜ʖ ͡°) (ง'̀-'́)ง (ノಠ益ಠ)ノ彡┻━┻ (ﾟ∀ﾟ) ಠ_ಠ Ho
by kevindeasis 10y ago
For git commit messages.
I've began liking to initiate or end a statement with stuff like these:
¯\_(ツ)_/¯
( ͡° ͜ʖ ͡°)
(ง'̀-'́)ง
(ノಠ益ಠ)ノ彡┻━┻
(ﾟ∀ﾟ)
ಠ_ಠ
How do you guys feel about these in git commit messages?
- pavel_lishin 10y agoIf they're relevant to the code change ("Not sure what I did, but the tests are passing now ¯\_(ツ)_/¯", "Removing production usernames and passwords from front-end config files, MIKE ಠ_ಠ"), it's fine. If I see a commit that's just "¯\_(ツ)_/¯", I will force-push over it, don't you even think about it.
- hellofunk 10y agoAnyone who writes these needs to have themselves, not the changes, committed.