search

FujiAPI / Fuji

Celeste 64 Mod Loader
30 stars 10 forks source link

Improve release workflow #74

Closed coolreader18 closed 5 months ago

coolreader18 commented 5 months ago

Basically now, if you want to create a release, push a commit to main that has release X.Y.Z somewhere in the subject line. Then, in the commit message body, put whatever changelog or text you want to go in the body of the github release.

See [https://github.com/coolreader18/Celeste64/releases/tag/0.5.0](an example release) generated by this workflow, and the workflow run that did it.

jasminegamedev commented 5 months ago

One additional question I just thought of. Since we are changing it to create the release before the builds happen, does that mean the draft will still get created, even if the build fails? I wonder if we might want to see if we can structure it in a way to avoid that. 🤔 Not a hard requirement, but just something we might want to consider.

coolreader18 commented 5 months ago

I noticed that as well - I could have a thing to delete the release if it fails.

jasminegamedev commented 5 months ago

I think this looks good to me now. We can see how it goes on our next release, and see if we need any more changes at that point. Merging.