[llvm] [Github] Add repository checks to release-binaries workflow (PR #84437)

[Aiden Grossman via llvm-commits]

boomanaiden154 wrote:

> Can you elaborate on what mechanisms are involved here? I remember seeing something on this topic somewhere, but don't remember the specifics. Forks of repos made after date X don't run scheduled actions automatically, unless fork user does Y to enable scheduled actions. Or did this extend to any kind of actions, e.g. ones with a regular `push:` trigger as well?

I believe it should be after a certain date (and that's what I remember). I can't find anything explicit in the documentation mentioning this though. There is just this paragraph:

> Warning: To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

There's also this screen that shows up on the actions tab when forking at least some repositories recently:

![image](https://github.com/llvm/llvm-project/assets/39388941/11bda040-44fc-4a30-9292-dae53051058e)

I can't find anything in the documentation about it though. From what I understand, scheduled workflows are disabled by default, but other workflow events are enabled by default (might have changed at some point though). Given the age of many LLVM forks though, a lot of workflows will just run, including scheduled workflows (hence this patch). We've found it's just good practice to restrict the repository jobs will run on to avoid this issue.


https://github.com/llvm/llvm-project/pull/84437