Closed calonmerc closed 1 year ago
I am not sure repo branch you are referring to. The CustomPiOS docker image branch? or your own branch?
You can decide which yaml would run on which brach on your repo: https://stackoverflow.com/a/72601918/311268
I'm referencing the git clone in the start_chroot_script within my repo.
You can create a config.local
file in the distro folder and set environment variables from there that are specific to the build. Then you can set the variable you created there PIFIRE_REPO_BRANCH
echo PIFIRE_REPO_BRANCH=devel >> /PiFireOS/src/config.local
Also you are welcome to add PiFireOS to the CustomPiOS readme list :) https://github.com/guysoft/CustomPiOS#list-of-distributions-using-custompios
Looks like that's what I was missing! Will report back after this test build runs!
I planned to request being added after I got the nightlies running on dev! Is there a proper process, or just follow the requests of others as a new issue?
I never reported back... that was definitely the fix I was looking for!
I'd like to leave the primary
release.yml
to pull a repo master, but the nightlybuild.yml
to pull the same repo but on development.Currently, images are building fine, but only pulling the master branch. I've been searching and testing on and off for a week. Wondering if there's a simpler way, maybe there's a way to know what *.yml is starting the build process?
I've looked through all existing modules in all listed builds based on CustomPiOS, but none are doing what I'm looking for.
Here's the repo, including the current GH action files