forked from maziggy/bambuddy
-
-
Notifications
You must be signed in to change notification settings - Fork 1
Branch Policy
Marko@VMHOMELAB edited this page Jun 13, 2026
·
1 revision
Printbuddy uses a development-first branch workflow.
-
dev: active development and validation branch. -
main: stable/release branch.
-
docker.io/vmhomelabde/printbuddy:latest: stable image from the release branch. -
docker.io/vmhomelabde/printbuddy:dev: development image for testing current work.
- Changes are developed on
dev. - Marko tests from
dev. - Approved changes are merged into
main. - Releases are cut from
main.
Use latest for normal deployments unless you intentionally want to test dev.