ChibiOS has moved from SVN to Git
Posted: Sun May 31, 2026 2:02 pm
ChibiOS has moved from SVN to Git
After many years on SourceForge Subversion, ChibiOS development has migrated to Git, hosted on GitHub. This is now the authoritative home for the source.
New repositories (under the chibios-upstream organization):
The ext/ and tools/ftl directories are Git submodules, so clone recursively:
If you already cloned without submodules, run:
SSH works too — the submodule URLs are relative, so they follow whatever protocol you cloned with.
For existing SVN users — what maps to what
About history
The Git repository carries a release-snapshot history: one commit per release, with all release tags preserved and their original dates. The full revision-by-revision SVN history is not reproduced in Git; it remains available in the SourceForge SVN repository, which stays online as a permanent, read-only archive:
The SVN repository is being frozen to read-only, so please do not rely on it for new commits.
Issues and tickets
Bug tracking moves to GitHub Issues on the chibios repository. We are importing the active (open and recent) SourceForge tickets; older and closed tickets remain in the SourceForge archive.
Contributing
Contributions are now made via fork and pull request on GitHub. Please remember to use --recurse-submodules when cloning your fork. The license is unchanged (GPL3 plus commercial, as before).
Thanks for bearing with the move. Git brings easier contribution, proper branching, and a smoother workflow for everyone.
After many years on SourceForge Subversion, ChibiOS development has migrated to Git, hosted on GitHub. This is now the authoritative home for the source.
New repositories (under the chibios-upstream organization):
- chibios — the OS itself: RT, NIL, HAL, SB, the test suites, demos and docs
- chibios-tools — ChibiStudio tooling
- chibios-ext — third-party libraries (FatFS, lwIP, littlefs, wolfSSL) as archives
- chibios-ftl — FreeMarker code-generation templates
The ext/ and tools/ftl directories are Git submodules, so clone recursively:
Code: Select all
git clone --recurse-submodules https://github.com/chibios-upstream/chibios.git
git clone --recurse-submodules https://github.com/chibios-upstream/chibios-tools.gitCode: Select all
git submodule update --init --recursiveFor existing SVN users — what maps to what
- trunk becomes the branch main
- branches/stable_XX.Y.x become the branches stable-19.1.x, stable-20.3.x, stable-21.11.x
- tags/verXX.Y.Z become the tags ver_XX.Y.Z (tag names were normalized to a consistent ver_ prefix)
Code: Select all
git clone --recurse-submodules https://github.com/chibios-upstream/chibios.git chibios
cd chibios
git worktree add ../chibios-stable-21.11.x stable-21.11.xThe Git repository carries a release-snapshot history: one commit per release, with all release tags preserved and their original dates. The full revision-by-revision SVN history is not reproduced in Git; it remains available in the SourceForge SVN repository, which stays online as a permanent, read-only archive:
Code: Select all
https://svn.code.sf.net/p/chibios/codeIssues and tickets
Bug tracking moves to GitHub Issues on the chibios repository. We are importing the active (open and recent) SourceForge tickets; older and closed tickets remain in the SourceForge archive.
Contributing
Contributions are now made via fork and pull request on GitHub. Please remember to use --recurse-submodules when cloning your fork. The license is unchanged (GPL3 plus commercial, as before).
Thanks for bearing with the move. Git brings easier contribution, proper branching, and a smoother workflow for everyone.
