https://nde-code.github.io/blog/en/tags/github/Recent content in GitHub on Nathan Debilloëz - BlogHugoenThu, 25 Jun 2026 00:00:00 +0000https://nde-code.github.io/blog/en/posts/how-to-clean-git-commit-history/Thu, 25 Jun 2026 00:00:00 +0000https://nde-code.github.io/blog/en/posts/how-to-clean-git-commit-history/<h1 id="introduction">Introduction:</h1> <p>This guide explains how to recreate a project&rsquo;s Git history from its current state by deleting the Git metadata from the local repository, initializing a new repository, and then replacing the history of the remote <code>main</code> branch.</p> <p>Although not common in day-to-day development, this operation is useful in several specific situations, for example:</p> <ul> <li><strong>Accidentally exposing secrets:</strong> always revoke them first (API keys, access tokens, passwords, etc.). Resetting the repository history helps remove them from the repository&rsquo;s visible history, but it <strong>does not guarantee</strong> that the data has disappeared from existing clones, <em>forks</em>, or caches.</li> <li><strong>Cleaning up a project:</strong> once the initial development phase is over, you may want to start with a clean history by removing the early work-in-progress <em>commits</em>.</li> <li><strong>Starting fresh after major changes:</strong> following a significant refactor or a long period of development, resetting the history can provide a clean baseline and make the repository easier to understand.</li> </ul> <p><strong>⚠️ Warning:</strong> this operation is irreversible. It will permanently overwrite the history of the remote <code>main</code> branch. If other people collaborate on this project, they should delete their local copy and clone the repository again once the operation is complete.</p>https://nde-code.github.io/blog/en/posts/introduction-to-the-blog/Sun, 21 Jun 2026 00:00:00 +0000https://nde-code.github.io/blog/en/posts/introduction-to-the-blog/<h1 id="preamble">Preamble:</h1> <p>I have wanted to create an articles section on my website for a very long time. Certainly not to talk randomly about certain topics or give my opinion on various things, but much more to explain, guide, or share my experience with certain digital or technological tools. This site goes by the &ldquo;name&rdquo; of a blog, but what I am going to do here is not really a blog—not by a long shot!</p>