For those of you who have custom image builds using the uBlue build template, how are you keeping your template build in sync with the action changes that are updated if you are using it?
I’m very interested if you are tracking updates to the template build scripts.
I’ve asked a question on the repo issues section regarding the engineering of a little update mechanism to include in the template. Appreciate it if you have any opinion on the matter. Thanks!
I’ve done a little “vibe coding” with Codex to see whether this could be done (I really wanted to see how good gpt5.3-codex was!). I put together a test template here: GitHub - Danathar/image-template: Build your own custom Universal Blue Image!
It includes a Sync Template GitHub Action you can trigger manually. The workflow pulls changes from ublue-os/image-template and should open a PR in your repo (created from the template) when there are syncable changes.
This uses AndreasAugustin/actions-template-sync: GitHub - AndreasAugustin/actions-template-sync: :octocat: Github action for syncing other repositories (templates) with current repository. Any git provider like GitHub (enterprise), GitLab, Gittea,.. are supported for the source repository
I’m holding off on opening an upstream PR until I finish more testing and review both the Andreas action and the workflow/files generated in my repo. In the meantime, feel free to template mine, run the action, and test it.
Good god this AI stuff is dangerous. I feel dumber just using it. Sure it saves a whole load of time, but how much did I REALLY learn? Not near as much as if I had hacked away on this on my own.
I said “Computer. Do make me mine code get friend changes. Me dumb. Do please”
And it did it… lol
You know, the funny thing is… I kinda haven’t been doing this. My repo is still largely the same as it was when I created my image in January of last year. Sure, I’ve done some housekeeping on it to make managing my customizations easier and to better align with upstream where it made sense, but a lot of that infrastructure has largely diverged at this point.
Which, to be honest, is kind of beautiful? The thing that really matters is the image that’s published by upstream, and I don’t really have to do anything to get the improvements being made there. It’s honestly a testament to the design, imo.
(Sure, my ISOs are still using the old anaconda installer w/o the live environment, and maybe I’ll go in and update it to use the newer iso builder at some point, but the marginal value of doing that for my image is rather minimal so it’s not really top of mind for me rn.)
Oh, they work—that’s for sure, but there are optimizations they have done to the template.
The only real concern, and granted I don’t think it’s a big one since we haven’t seen an issue that would impact older templates, is that there is a non-zero possibility of a change that GitHub rolls out that would require a change to the template and that would break older templates people have used, which is one reason why I proposed it an update mechanism to sync changes.