From b393100c6aa9e19970735142d281cb671109c128 Mon Sep 17 00:00:00 2001 From: SindreKjelsrud Date: Wed, 25 Jun 2025 19:19:19 +0200 Subject: [PATCH] feat(blogpost): New blogpost! "no more gitmojis" Signed-off-by: SindreKjelsrud --- src/content/blog/no-more-gitmojis.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 src/content/blog/no-more-gitmojis.md diff --git a/src/content/blog/no-more-gitmojis.md b/src/content/blog/no-more-gitmojis.md new file mode 100644 index 0000000..287fe52 --- /dev/null +++ b/src/content/blog/no-more-gitmojis.md @@ -0,0 +1,22 @@ +--- +title: "no more gitmojis" +pubDate: 'Jun 25 2025' +description: "" +draft: false +--- + +the time has come. + +i've chosen to no longer use [gitmojis](https://gitmoji.dev). + +as you may know from my blog post last year about _[why i like small commits](/blog/why-i-like-small-commits/)_, i used to like using them as a way to identify the purpose of the commit. + +they've been my go to for styling commits for the past two years now, but not anymore! + +i've gone back to my old ways of using [conventional commits](https://conventionalcommits.org/): _"a specification for adding human and machine readable meaning to commit messages"_. + +it will help me spend less time finding that perfect emoji for my commits, even though this makes the commit log not look as flashy as it used too. but hey, at least it's easier to understand the commit log for the one person who might check out my repos. + +also it's basically what i use professionally, with the additional Jira-task instead sometimes (e.g. "JIR-420: no more gitmojis ;("). + +you'll be missed, gitmoji <3 \ No newline at end of file