continueOnMissingPermissions should continue when repoToken is missing?

[fgdorais]

Perhaps continueOnMissingPermissions should continue when repoToken is missing?

The end purpose is to prevent this action from running on forks since that doesn't make sense in many use cases. Setting continueOnMissingPermissions does this and allows for exceptions where necessary permissions can be granted.

However, when the main repo uses MY_SPECIAL_TOKEN instead of something that exists in every repo, then the failure is missing input not missing permissions. I think continueOnMissingPermissions should handle this as if it were missing permissions and fail gracefully. The permissions are evidently missing in that case too!

[eps1lon]

It used to be that forks only get a read-only token. Is that no longer the case?

If forks still get a read-only token, a missing token would be a misconfiguration that we should catch with an error.