<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>D// #13 (Posts about Git)</title><link>https://alcacer.de/</link><description></description><atom:link href="https://alcacer.de/categories/git.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:hello@alcacer.de"&gt;Dorian&lt;/a&gt; </copyright><lastBuildDate>Tue, 25 Nov 2025 17:07:24 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Gitmoji</title><link>https://alcacer.de/posts/gitmoji/</link><dc:creator>Dorian</dc:creator><description>&lt;div&gt;&lt;p&gt;I'm still a total fan of Chris Beam's  &lt;a href="https://cbea.ms/git-commit/"&gt;How to Write a Git Commit Message&lt;/a&gt; but lately I mixed in some &lt;a href="http://gitmoji.dev"&gt;gitmojis&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Gitmoji support is available at different levels (e.g. GUI git clients like Tower App), but I prefer the &lt;a href="https://github.com/carloscuesta/gitmoji"&gt;command line tool&lt;/a&gt;. My current workflow is to stage everything with &lt;a href="https://www.sourcetreeapp.com"&gt;Sourcetree&lt;/a&gt; and then fire up an interactive &lt;code&gt;gitmoji -c&lt;/code&gt; to give a special touch to my commit message.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;gitmoji -l&lt;/code&gt; will listen all of the avilable messages, just like the website would do.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://alcacer.de/posts/gitmoji/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>Git</category><guid>https://alcacer.de/posts/gitmoji/</guid><pubDate>Thu, 10 Apr 2025 08:00:08 GMT</pubDate></item><item><title>Sphinx Markdown Mermaid Preprocessor</title><link>https://alcacer.de/posts/sphinx-markdown-mermaid-preprocessor/</link><dc:creator>Dorian</dc:creator><description>&lt;div&gt;&lt;p&gt;Last year, we migrated all our companies documentation to markdown rendered via &lt;a href="https://www.sphinx-doc.org/"&gt;sphinx&lt;/a&gt;. Because of &lt;a href="https://gitlab.com/"&gt;Gitlab&lt;/a&gt; and &lt;a href="https://typora.io"&gt;Typora&lt;/a&gt; we are a little bit spoiled and wanted to keep our good looking &lt;a href="https://mermaid-js.github.io"&gt;mermaid js graphs&lt;/a&gt; - needles to say, that this was not supported by &lt;a href="https://www.sphinx-doc.org/"&gt;sphinx&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://alcacer.de/posts/sphinx-markdown-mermaid-preprocessor/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>Git</category><category>gitlab</category><category>markdown</category><category>mermaid</category><category>Python</category><category>sphinx</category><category>til</category><guid>https://alcacer.de/posts/sphinx-markdown-mermaid-preprocessor/</guid><pubDate>Mon, 20 Apr 2020 13:00:53 GMT</pubDate></item></channel></rss>