<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Git on TACE Data</title><link>https://tacedata.ca/tags/git/</link><description>Recent content in Git on TACE Data</description><generator>Hugo</generator><language>en-CA</language><copyright>2026 TACE Data Management Inc.</copyright><lastBuildDate>Sat, 04 Apr 2026 06:00:00 +0000</lastBuildDate><atom:link href="https://tacedata.ca/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>security - stage 2 - internet cache and the wayback machine</title><link>https://tacedata.ca/posts/sec-stage-2-post/</link><pubDate>Sat, 04 Apr 2026 06:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/sec-stage-2-post/</guid><description>Cleaning git history removes data from your repo — but not from search engines, the Wayback Machine, or GitHub&amp;rsquo;s cache. Here is what to check.</description></item><item><title>security - stage 1 - cleaning sensitive data out of git history</title><link>https://tacedata.ca/posts/sec-stage-1-post/</link><pubDate>Sat, 04 Apr 2026 01:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/sec-stage-1-post/</guid><description>After a security review flagged AWS identifiers committed to a public repo, we used git-filter-repo to scrub them from all 46 commits — including file content and commit messages.</description></item><item><title>security remediation — what we got wrong</title><link>https://tacedata.ca/projects/security-remediation-proj/</link><pubDate>Sat, 04 Apr 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/projects/security-remediation-proj/</guid><description>A post-launch security review of tacedata.ca uncovered sensitive AWS identifiers committed to a public repository. This is a full account of what was exposed, how it was found, and what it took to fix it.</description></item></channel></rss>