Closed JannisPetschenka closed 1 year ago
Hmm... Maybe I'll just move the installation of the needed packages into the respective action. Seems easier than hosting a docker image that I usually forget to update
Hmm... Maybe I'll just move the installation of the needed packages into the respective action. Seems easier than hosting a docker image that I usually forget to update
True, might be easier.. But here is a way to do it via an action GitHub Docker action.. I could look into it a bit more next weekend if you'd like.
True, might be easier.. But here is a way to do it via an action GitHub Docker action.. I could look into it a bit more next weekend if you'd like.
Wouldn't the main image be updated then? Or can you create different sub-tags and delete them on merge?
Wouldn't the main image be updated then? Or can you create different sub-tags and delete them on merge?
Hmm true.. you could build/use the images locally in the action when on sub-branches and only push to docker-hub when on main. But I think that would still be a bad idea since that would mean you'd push the images everytime you push to main. Even if there were no changes to the dockerfiles (which I assume is the case 90% of the time). So manually might be the way to go :)
Fixed the issues and added the additional dependencies to the build files, should hopefully work now :)
Got the next PR already prepared :) It should be a bit more straight forward since it's pretty much just your code from SwaySettings with some stuff removed ;)