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

Aiden Grossman via llvm-commits llvm-commits at lists.llvm.org
Fri Mar 8 00:05:01 PST 2024


boomanaiden154 wrote:

> Hmm, right. It's a bit non-obvious that there's a distinction between whether a repo did have actions at the point when it was forked or not, but I guess it makes sense. Thinking further, it would be nice if there was an explicit setting that one can set on one's fork, to disable/enable scheduled actions...

Definitely. I wish it was better documented (or that I was better at finding the documentation if it exists). There are explicit settings that do exist.

https://docs.github.com/en/actions/using-workflows/disabling-and-enabling-a-workflow shows how to enable and disable specific workflows. This requires knowing what workflows are interesting to disable though.

By going into settings->actions->disable actions, you can also disable all actions in your fork. I believe this shouldn't impact any upstream contributions as the `pull_request` target should be from the workflow definition in the target branch.

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


More information about the llvm-commits mailing list