<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on ads' corner</title><link>https://andreas.scherbaum.la/tags/git/</link><description>Recent content in Git on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Jul 2025 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>check-markdown-files: pre-commit checks for blog postings written in Markdown</title><link>https://andreas.scherbaum.la/post/2025-07-28_check-markdown-files-pre-commit-checks-for-blog-postings-written-in-markdown/</link><pubDate>Mon, 28 Jul 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-07-28_check-markdown-files-pre-commit-checks-for-blog-postings-written-in-markdown/</guid><description>&lt;p&gt;I wrote a thing which helps me write better blog postings.&lt;/p&gt;&#10;&lt;p&gt;After &lt;a href="https://andreas.scherbaum.la/post/2023-11-25_new-blog"&gt;switching my blogs&lt;/a&gt; from S9Y to a static blogging engine (&lt;a href="https://gohugo.io/"&gt;goHugo&lt;/a&gt;), I found a number of preventable issues. Certain syntax errors, forgot tags, or forgot a description, or forgot a preview picture, or forgot an image. This kind of things. So I wrote &lt;a href="https://github.com/andreasscherbaum/check-markdown-files"&gt;check-markdown-files&lt;/a&gt;, which now scans all my blog postings before committing the posting to &lt;code&gt;git&lt;/code&gt;. Any known error is raised, and aborts the commit. Each problem has an override switch in case it is a false positive.&lt;/p&gt;</description></item><item><title>GitHub Actions: Node.js 12 actions are deprecated</title><link>https://andreas.scherbaum.la/post/2023-01-13_github-actions-node.js-12-actions-are-deprecated/</link><pubDate>Fri, 13 Jan 2023 16:42:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2023-01-13_github-actions-node.js-12-actions-are-deprecated/</guid><description>&lt;p&gt;If you use &lt;a href="https://github.com/features/actions"&gt;GitHub Actions&lt;/a&gt; to run Workflows and tests, you might have spotted this warning recently:&lt;/p&gt;</description></item><item><title>GitHub Actions: The `set-output` command is deprecated and will be disabled soon</title><link>https://andreas.scherbaum.la/post/2023-01-10_github-actions-the-set-output-command-is-deprecated-and-will-be-disabled-soon/</link><pubDate>Tue, 10 Jan 2023 13:42:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2023-01-10_github-actions-the-set-output-command-is-deprecated-and-will-be-disabled-soon/</guid><description>&lt;p&gt;If you use &lt;a href="https://github.com/features/actions"&gt;GitHub Actions&lt;/a&gt; to run Workflows and tests, you might have spotted this warning recently:&lt;/p&gt;</description></item><item><title>git pre-commit Hooks</title><link>https://andreas.scherbaum.la/post/2020-10-25_git-pre-commit-hooks/</link><pubDate>Sun, 25 Oct 2020 20:29:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-10-25_git-pre-commit-hooks/</guid><description>&lt;p&gt;A very common use case for hooks in &lt;a href="https://git-scm.com/"&gt;git&lt;/a&gt; is a &lt;code&gt;pre-commit&lt;/code&gt; &lt;a href="https://git-scm.com/docs/githooks"&gt;hook&lt;/a&gt;. This hook is used to verify the to-be-committed data before it is added to the repository.&lt;/p&gt;</description></item></channel></rss>