Clear and consistent naming helps us move fast without confusion. Stick to these conventions to keep things simple and maintainable.
<type>/<short-name>
feature– New functionalitybugfix– Fixing a bugrefactor– Improving code without changing behaviordoc– Documentation updatestest– Adding or updating testsinfra– Dev tools, scripts, CI/CD, or build system changeshotfix– Emergency production/staging fixes
feature/apogee-estimatorbugfix/altimeter-spikerefactor/imu-state-machinedoc/telemetry-readmetest/unit-altitude-handlerinfra/flash-script-improvementshotfix/fix-bad-data-packet
<type>: <concise description>
Keep the message short and action-oriented. If needed, add more detail in the commit body.
feat– New featurefix– Bug fixref– Refactoringdocs– Documentationtest– Test codeinfra– Tooling or CIchore– Minor cleanup or version bumpshotfix– Emergency patch
feat: add apogee prediction modulefix: correct telemetry packet sizeref: clean up finite state machinedocs: add README for ground stationtest: add IMU integration testinfra: update flash deploy scriptchore: remove unused enumshotfix: handle altimeter overflow