for me it lists the recipes, but the default is the first recipe in the justfile, so maybe you're us
for me it lists the recipes, but the default is the first recipe in the justfile, so maybe you're using some justfile without a proper first recipe
Xthis is mine
EThat would be a new one. I can't look into it now but I can later
TI'm guessing you're getting back a 404 page from some url that's part of the repo
ELooks like just 37. I can look into that as well but need a bit
EI'm thinking it might have moved
EOr was dropped
Scould you give me your whole just file?
XThat is my whole justfile
Sah ok
S;3
XIt just includes other justfiles from bling
Show do you like deploy those justfiles?
Slike
MYou can run just -l to force list recipes
Xwhat do you mean?
Slike could you give your custom justfiles?
Slike the custom.just
Xmain.just is from the main image, nvidia.just is from the nvidia image, custom.just is from startingpoint
Xcustom.just includes bling.just https://github.com/ublue-os/startingpoint/blob/template/usr/share/ublue-os/just/custom.just
Xwhich includes lots of bling justfiles
Sah ok thanks :3
XI'm trying to create an ISO release action for startingpoint based on the examples in isogenerator, release_please, and main, but I can't really figure out how it should work.
Xrelease-please creates a "release PR" that creates a changelog with the commits, but doesn't actually then create a release, and build-iso is skipped because a release wasn't created...
ARelease please will create a release after the release PR has been merged not before
ALet me know if I can help you somehow 
XI did merge it on my testing repo and nothing happened
XWell, you can either cook up a PR for this one or help me figure it out
XThis is the worflow rn https://github.com/EinoHR/linuXYZ/blob/iso/.github/workflows/release-iso.yml
AIt is working?
XOk, I ran it again and apparently it is working now.
XIs the workflow like: run action once, PR gets created, rerun, release gets created, ISO built
AYes
AOn normal commits it will detect changes and add it to the release PR
AWhen you merge that one then the release gets created
XSo the release PR should always exist and then when merged the release action should be ran again to release and create the new PR?
AYes
AActually it will only create the PR on the next commit after it creates a release
ANormal commit -> add to release PR or create one if not exists
Release commit -> create release and trigger iso build
Release commit -> create release and trigger iso build
XSo is there something I should change in the PR to make it do all that automatically so I don't need to workflow_dispatch twice every release? Is it possible to make it so the user of the template can just press one button and the release will be made and ISO built?
XFor most people the release-please convcommits stuff does not really matter, since the ISOs always pull the latest version, correct?
XAlso, the recent action run failed but I'm unable to see what the error is. Or rather; It's a python runtime error in isogenerator, and I don't know what caused it. My understanding is that not providing a boot menu should just use the one in the isogenerator repo, and other than that it's basically the example with the ublue-os org related things replaced with ${{ github.repository_owner }}
XADon't use release please if this is the net result you want imo
ANo you need to provide a boot_menu.yml
AOr maybe that changed 
let me check
let me checkAYeah it is required
XOk
AThat's a very ugly error message huh
XHmm, well, it is useful for some situations, but is there something you recommend instead?
Arelease-please requires understanding git tagging as it is supposed to overtake the entire release process basically
