perfect, I love when we're like "oh nice work person who thought of that!"
perfect, I love when we're like "oh nice work person who thought of that!"
Jinvesting in our future selves!
Jok
Bisgenerator is doing a pretty serious test
Jyeah so experimental is nice because we don't check anything, you can just merge right to main, so it's awesome for testing actions and things that would need review, etc.
Bfree to explain this to me?
Bthe isogenerator action... does it need a release to be available for experimental to use?
Bah, no, it's using main... so... i hope that means @main branch
https://github.com/ublue-os/experimental/blob/fc656e7de84f09072f00030bf91ce648028c8bfc/.github/workflows/release-please.yml#L31
https://github.com/ublue-os/experimental/blob/fc656e7de84f09072f00030bf91ce648028c8bfc/.github/workflows/release-please.yml#L31
Bso... I deleted
but looks like it skipped ISO generation
https://github.com/ublue-os/experimental/actions/runs/5019784688/jobs/9000641600
test3.md to generate a build in experimental...but looks like it skipped ISO generation
https://github.com/ublue-os/experimental/actions/runs/5019784688/jobs/9000641600
BJI see it building?
JGitHub
Don't use me. Contribute to ublue-os/experimental development by creating an account on GitHub.
Byeah, that's doing a container build, not ISO
Jdid the release-please PR open the release PR?
Bhmm... not yet, will that happen after container build sucess?
Jmaybe lemme check
Bugh, i didn't use semantic commti message
Jwait we turned that off
Jsec
Bok, i was just guessing
Jsec lemme clean up some trash
Bdang... let somthing sit a couple months and we forget how to use it 
(to be fair, i've never used it)
(to be fair, i've never used it)Jok so down to the 2 workflows
Jthose ones cluttering the left columns are last runs from other older stuff, they don't reflect what's in the repo
Bk
Jtldr copied the action from main->experimental
Bk
Bi think the problem is what you said earlier... "release-please" didn't create a release
Jyeah
Jbut also the action didn't even use the isogenerator, it's from some old thing
Jso "resyncing" basically
Buses: ublue-os/isogenerator@main that looks correctJok, delete test4.md and do a semantic pr just to make sure
B
BFOR GREAT JUSTICE!
Bit needed a sematic "feat:" or something it considered "user facing"
Bthis is kinda cool 
i never played with these toys before
i never played with these toys beforeBexperimental ISO generation commencing! https://github.com/ublue-os/experimental/actions/runs/5019874164/jobs/9000820399
PBand failing
Bapparently we have a specific mirror hard coded and it no worky no more
Buff
Bso we need new mirror
Bto hardcode
Bseems that way
Bno branch rules on the isogenerator... so i just merged my own PR
Bthe problem is in this experimental repo, it's putting the wrong version into the URL template
Bi got past that
Bnow a new bug
B... i'm not really sure
