<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🗂️ Never lose a working build again]]></title><description><![CDATA[<p dir="auto">When a device fails in the field, the first question is: "what exact binary is on it, and can we rebuild it?" If your version control can't answer that, nothing else in your workflow matters.</p>
<h3>Checklist before you ask for help here</h3>
<ul>
<li><div class="plugin-markdown"><input type="checkbox" /></div><strong>Every shipped binary maps to a tag</strong> (<code>git tag v1.2.3</code>), not "final_final2". A tag is the only way to rebuild byte-identical firmware months later when a customer reports a bug on old hardware.<br />
→ <a href="https://embiq.grapesiot.com/engineering-tools-professional-skills/36-git-version-control/chapter-04" rel="nofollow ugc">Tags, releases and repository hygiene</a></li>
<li><div class="plugin-markdown"><input type="checkbox" /></div><strong>Build artefacts, secrets and calibration dumps are ignored.</strong> <code>.pio/</code>, <code>build/</code>, certificates, tokens and per-device calibration data never belong in history. Once a secret is committed, rotating it is the only fix — deleting the file later doesn't remove it from history.</li>
<li><div class="plugin-markdown"><input type="checkbox" /></div><strong>No credentials in the repo. Ever.</strong> Device tokens and WiFi passwords live in provisioning, environment, or a secrets store — not in a header file someone will push to GitHub.</li>
<li><div class="plugin-markdown"><input type="checkbox" /></div><strong>You can bisect back to the breakage.</strong> When a regression appears three weeks late, <code>git bisect</code> with small, honest commits finds the culprit in minutes. "Backup Friday" commits make that impossible.<br />
→ <a href="https://embiq.grapesiot.com/engineering-tools-professional-skills/36-git-version-control/chapter-05" rel="nofollow ugc">Advanced workflows and recovery</a></li>
</ul>
<hr />
<p dir="auto"><em>Start at <a href="https://embiq.grapesiot.com/engineering-tools-professional-skills/36-git-version-control/" rel="nofollow ugc">Git &amp; Version Control</a> and work through it in order. Share your workflows, ignore-file setups, or mistakes learned the hard way. Tag with <code>git</code>.</em></p>
]]></description><link>https://forum.grapesiot.com/topic/72/never-lose-a-working-build-again</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 13:02:44 GMT</lastBuildDate><atom:link href="https://forum.grapesiot.com/topic/72.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Oct 2026 11:29:38 GMT</pubDate><ttl>60</ttl></channel></rss>