Tyrrrz
commented
9 months ago Hi. This is expected, since you would need to provide your own token for it to work on a fork, or remove the test job entirely. Forking a repository does not guarantee that the corresponding workflows will work out of the box (most of the time they won't). If you want to skip the workflow, you should do it in your fork. Here, I want the workflow to fail if any of the secrets are missing, because that would indicate that there's an issue (except on PRs).
Forking this repository leads to the CI workflows failing on the fork, since forks won't have access to the necessary token. This fixes that by simply skipping the failing workflow in such cases. Also, a minor gitignore update slipped in while I was at it, too.