New comment by dmarto on void-packages repository

https://github.com/void-linux/void-packages/pull/37339#issuecomment-1141457399

Comment:
You can stop *all* actions from the settings of your fork (if you don't want them), while if you want to keep them, you will have to maintain a commit that undoes that. I for one, want to keep the cycle action in my fork, as I do use my master branch for personal packages. 

And in general, I am not a fan of embedding such "code actions" i.e the code shouldn't care in which repo it is or who is the owner of the repo. At least in my mind, when I fork something I expect 1:1. (off-topic, I bet some may will find it fun to use an action that deletes commit if inside forks - DRM by GithubAction (trademark pending))

Anyway, if the larger consensus is that this is better, I won't be mad or sad; I will simply revert it for myself. 

P.S
```yaml
if: github.repository_owner == 'void-linux' || github.event_name != 'schedule'
```
is a more clear version (disclaimer, not tested).

---
EDIT

For the `stale` workflow, it does make sense to have it disabled; and there for sure isn't any use inside forks. 

On another note, most existing forks will probably never get this change; as most people fork and rarely update (and push) master, so if the reason is saving resources for GitHub, it is not a good reason.