Contribute
Submitting changes
Small branches off main, a pull request, a review. main always builds and runs.
Branches
feat/<thing>for new work (feat/agent-heartbeat),fix/<thing>for bug fixes,chore/<thing>for tooling, dependencies and docs.- Branch off
main, merge back within days. Rebase onmainbefore opening the pull request. - Pull requests are squash-merged, so
mainreads as one commit per change.
Before a pull request
npm run buildpasses (it typechecks the web app and the server).cd agent && go test ./...passes, if you touched the agent.- The screens you touched look right: dark and light, wide and phone-width.
CLAUDE.mdorPLAN.mdupdated if you changed how something works or decided something, with the date.- This wiki updated if what people see or do changed.
Review
Every pull request is reviewed. Anything touching enrollment, certificates, agent commands, agent updates or the vault needs a review that reads the code end to end, not a skim: an RMM is a key to every machine it manages.
The wiki itself
It's in wiki/: plain HTML, no build. wiki/README.md says how to preview it and add a page. If something here is wrong, a pull request that fixes it is the best report.
Licence
CERMM's licence hasn't been chosen yet. Until it is, ask before building anything of your own on the code. Once outside contributions are taken, they'll need a contributor agreement (a CLA or DCO), which will be described here.