Forks of this repository spam contributors with failing CI jobs

[JLLeitschuh]

Description of the issue

https://github.com/JLLeitschuh/ql/actions/runs/3301731539
https://github.com/JLLeitschuh/ql/actions/runs/3301299877

Any chance these CI jobs could check the org they are running against and just disable/skip/not fail in those cases?

[jketema]

Hi @JLLeitschuh. Workflows are disabled by default when forking a repository, so it seems you explicitly enabled them for some reason. I guess we could in principle check for the org on all our workflows, but that's probably going to mean that all the workflows are going to be no-ops on your fork, which is probably not what you want either. Otherwise, why did you enable them? The best solution here is probably to disable individual workflows on your side, as described here: https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow. Does this help?

[intrigus-lgtm]

As another data point, all actions work just fine in my repo:
https://github.com/intrigus-lgtm/ql/actions
Maybe try updating the main branch?