GitHub Actions runs publish_container.yml periodically from forked project

[lahwaacz]

I have a forked project and just noticed that GitHub Actions runs something periodically:

https://github.com/lahwaacz/hyperqueue/actions/runs/13252379042

It failed on the Tag and push image step because I obviously don't have access to push to ghcr.io/it4innovations/hyperqueue 🙈

Please reconfigure it such that it does not run from fork projects.

[Kobzol]

Hi, you can disable CI on forks, in fact I think that it's disabled by default.

[lahwaacz]

I don't remember enabling CI in this fork. I have probably forked it a long time ago and recently just synchronized the content, including this new CI configuration...

In any case, this CI workflow feels very weird. Some forks may want to enable CI, except for this one workflow that pushes to your image registry, and forcing them to change the configuration is not very fork-friendly 🤷

[Kobzol]

When I need to run CI on a fork, I usually just modify CI to suit my needs and avoid things like this. But it doesn't really cost us anything to solve this upstream, so here you go :) #814