Disable AArch64 jobs on forks

[waj]

Now that #9508 is merged, the workflow is being executed on every commit, even on repository forks. I don't know a better way to disable it. I tried with an environment variable, but seems like unfortunately they are not available at the job.if level.

[jhass]

Well, only when the fork enables GitHub actions in the first place.

Why would you disable only the AArch64 workflow like this and not the others?

[oprypin]

@jhass because it can't actually run without separate hardware

[jhass]

Ah well. Is this really an issue? Can't you just ignore the failures? For a long-term fork, disabling the workflow there is also super easy.

[waj]

I found running the workflows in my fork is quite useful actually. The specs are executed even before sending the PR without any extra configuration.

[jhass]

If the jobs are skipped like this, are they rerun once you open a PR to branch?

[waj]

If the jobs are skipped like this, are they rerun once you open a PR to branch?

Apparently, yes. They were run on this PR and skipped on my repo: https://github.com/waj/crystal/runs/843517722

Can't you just ignore the failures?

Sure, but it's annoying to see a red flag on every commit.

For a long-term fork, disabling the workflow there is also super easy.

I don't see any way that isn't deleting the yml file. GitHub is adding features to Actions all the time and I guess this might be a quite common issue. It wouldn't be strange that they add a better way to deal with this in the future, but for now seems to be an acceptable workaround to me.

[Blacksmoke16]

I don't see any way that isn't deleting the yml file

Probably can go to Settings => Actions on your fork and choose the last option:

[waj]

@Blacksmoke16 I know. I meant disabling just the AArch64 workflow.

[jhass]

Oh well, I really hope GH gets the story straight on self hosted runners. Too many edge cases.