Doing a different approach to CI, as am redoing the steps inside the workflow as opposed to building the dockerfile and running it.
Upside is that docker doesn't run inside the CI, downside is that if build steps have to change, they must be changed in both the workflow file and the dockerfile as opposed to only modifying the dockerfile.
(imo i do prefer the other docker-based pr since it takes less to maintain, as any changes to the dockerfile also get reflected in the ci)
Description
Adds a GitHub Actions workflow to automatically build a CIA upon commits to n3ds-main
Also fixes a perms issue on the scripts that prevents the Dockerfile from being built
Also fixes bannertool download in the Dockerfile
Purpose
Would be useful for releasing nightly builds of this app without having to compile it yourself. Could also be integrated into Universal Updater by having it create a "nightly" release in GitHub Releases, tho that isn't currently implemented in this PR.
Alternative to #12
Doing a different approach to CI, as am redoing the steps inside the workflow as opposed to building the dockerfile and running it.
Upside is that docker doesn't run inside the CI, downside is that if build steps have to change, they must be changed in both the workflow file and the dockerfile as opposed to only modifying the dockerfile.
(imo i do prefer the other docker-based pr since it takes less to maintain, as any changes to the dockerfile also get reflected in the ci)
Description Adds a GitHub Actions workflow to automatically build a CIA upon commits to n3ds-main Also fixes a perms issue on the scripts that prevents the Dockerfile from being built Also fixes bannertool download in the Dockerfile
Purpose Would be useful for releasing nightly builds of this app without having to compile it yourself. Could also be integrated into Universal Updater by having it create a "nightly" release in GitHub Releases, tho that isn't currently implemented in this PR.