Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Embiq Community

  1. Home
  2. Knowledge Base
  3. Git & Version Control for Firmware
  4. šŸ—‚ļø Never lose a working build again

šŸ—‚ļø Never lose a working build again

Scheduled Pinned Locked Moved Git & Version Control for Firmware
gitversion-controlfirmware
1 Posts 1 Posters 86 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    admin
    wrote on last edited by
    #1

    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.

    1 Reply Last reply
    0

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better šŸ’—

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    Powered by NodeBB Contributors
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups