Skip to content
  • 0 Votes
    1 Posts
    86 Views
    A
    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. Checklist before you ask for help here Every shipped binary maps to a tag (git tag v1.2.3), 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. → Tags, releases and repository hygiene Build artefacts, secrets and calibration dumps are ignored. .pio/, build/, 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. No credentials in the repo. Ever. Device tokens and WiFi passwords live in provisioning, environment, or a secrets store — not in a header file someone will push to GitHub. You can bisect back to the breakage. When a regression appears three weeks late, git bisect with small, honest commits finds the culprit in minutes. "Backup Friday" commits make that impossible. → Advanced workflows and recovery Start at Git & Version Control and work through it in order. Share your workflows, ignore-file setups, or mistakes learned the hard way. Tag with git.