Developing PatchMon
How to build, test and release PatchMon. The mechanics of working on the codebase, as opposed to the process of contributing, which lives under How we work.
MI
By M. Ibrahim (Admin)·5 articlesWhat happens when you open a pull requestThe checks that run on a pull request, what each one is actually testing, the extra approval step for forks, and the test image you get to try the change for real.
5 min readHow a release happensThe GitHub release page is the source of truth for release notes. What publishing a release triggers, and why you should never hand-write release notes or push a tag.
4 min readHow versioning worksNo source file in PatchMon declares a version. The git tag is the only source, injected at build time. How edge builds are versioned as a pre-release of the next patch, and what to do when you see 0.0.0.
6 min readBuilding PatchMon locallyThe three build paths (server, agent, Docker image), what each one produces, and how to run the stack for development.
4 min readHow work gets planned and shippedThe engineering view of both work streams: how a feature request becomes a GitHub issue, how a bug is triaged, and what has to be true before either is done.
6 min read