Osiris-Team
Support for Dev/Branch GitHub Actions Builds for Mod and Plugin Updating (Using Artifacts Generated by Workflows)
Importance: 6/10
Problem: Some people may prefer to use a dev or beta build. A lot of developers build their software on GitHub automatically using GitHub Actions. When those run on the main branch it will generate a compiled JAR after every commit which is the dev build based on the latest branch changes. Right now for example I want to use the DriveBackupV2's plugin dev build since this fixes some issues but it's only available as artifact from GitHub Actions.
Solution: Add support for this. The artifact needs to be downloaded and then unzipped and then the JAR file is inside. This is because GitHub Actions makes the artifacts in ZIP files, and doesn't rawly upload the files directly. So it'd be needed to include an extraction/unZIP function. So it's needed that we can somehow fetch the latest artifact from a workflow from a certain repository (there could be multiple workflows so there needs to be done some stuff to resolve conflicts as those), unZIP the artifact and then move the new JAR file from inside the artifact to either the plugins or mods folder, depending on the type that has been downloaded.
Yeah this sounds great, feel free to create a PR!
I will look into it. It will probably however take a while, since this may need a lot of functions to implement.