Bthanks guess we missed that one
Jyeah we need to move to groups, etc.
Clol
Bi know it' s not pretty but i think this is all we need https://github.com/ublue-os/isogenerator/pull/65/files
Bi really want to just run this locally to generate an ISO before we even merge that
Junderstood
Bi'm just trying to see HOW
Jwe could generate it in experimental
Boh! ok, i've not used experimental
Bbut that sounds good
Btty easier for this?
Jsec
B30 seconds here
Jno branch rules in the repo
Jso I would just copy and paste the build action that calls the iso generator and make a release
Joh it's up to date already
JI wonder if we can just hit the button
Bi'm confused
Jwe can generate an iso from this repo to test
Bok, so we need to merge isogenerator first?
Jyeah or call a specific revision in the action, which is probably what you want
Bok, ready to merge and we'll ahve experimental call it
Jwe can merge it, all we need to do is not make a release from main/nvidia which is an explicit process anyway
Bmain's use of isogenerator is tagged to v2.0.0
Jperfect, 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
