<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Integrity on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/code-integrity/</link><description>Recent content in Code Integrity on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 23 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/code-integrity/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 14: Git Security Best Practices and GPG Signing</title><link>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-14-git-security-gpg/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/git-github-mastery-2025/chapter-14-git-security-gpg/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 14! So far, we&amp;rsquo;ve explored the core mechanics of Git, mastered branching strategies, resolved conflicts, and collaborated effectively. But how do we ensure the integrity and authenticity of our work, especially in a world where security threats are ever-present? That&amp;rsquo;s exactly what we&amp;rsquo;ll tackle today.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll dive deep into Git security best practices. Our main focus will be on &lt;strong&gt;GPG (GNU Privacy Guard) signing&lt;/strong&gt;, a powerful technique that allows you to cryptographically sign your commits. This ensures that your commits are truly from you and haven&amp;rsquo;t been tampered with. Think of it as a digital seal of authenticity on your code contributions. We&amp;rsquo;ll also touch upon other critical security considerations for your Git workflows.&lt;/p&gt;</description></item></channel></rss>