> > I think the current restrictions are OK. Perhaps we could auto-update the > > image based on CI but I wouldn't trigger that from Geany repos but this > > repository (this is where the dockerfile is after all). > > Sounds good to me.
I added a CI workflow on this repository to build the Docker image on push events and on a weekly schedule. For now, the image is configured as private and so it can be used only from within the organization. In particular this means that pull requests for Geany or G-P which are created from a forked clone, cannot access the Docker image. For this, we need to make it public. This should be ok but I would wait a bit until the new process works as expected. Once an image is made public, it cannot be deleted anymore. -- Reply to this email directly or view it on GitHub: https://github.com/geany/infrastructure/pull/7#issuecomment-1288098361 You are receiving this because you are subscribed to this thread. Message ID: <geany/infrastructure/pull/7/c1288098...@github.com>
