Open pull requests against the integration branch (the default branch),
not main. main stays close to the upstream lvgl_micropython layout;
integration is the curated branch that aggregates the MicroPythonOS-specific
deltas and is what MicroPythonOS builds consume.
Conventions:
- Branch names:
feat/<name>orfix/<name>for focused changes; long-running work lives ontopic/<name>branches (see the "MicroPythonOS Branching Model" section in the README for the current list and the merge flow). - Build-time patches: changes that MicroPythonOS applies at build time
(to
lib/micropython,lib/lvgl, or this repo's own files such asbuilder/) are committed as.patchfiles in the repo root and applied by MicroPythonOS'sscripts/build_mpos.sh— add the.patchhere and open a companion PR there. The mechanism, the current list, and the add/update/verify workflow are documented once in the MicroPythonOS docs: Build-time Patches. - Custom fonts: regenerate via
lib_lvgl_src_font/regenerate_fonts.sh(seelib_lvgl_src_font/README.md); don't hand-edit generated.cfiles. mainchanges: only cross-cutting documentation belongs there; everything else goes tointegrationor a topic branch.
Building and testing happens through the
MicroPythonOS super-repo
(scripts/build_mpos.sh), which pins this repository as a submodule — see
its docs for desktop/device build instructions. Heed the warning at the top
of this repo's README about submodule handling when cloning standalone.