Extend "on" with possibility to ignore forks (run only for the original repo) and vice versa

[famod]

Hi, I was redirected here from actions/runner#859:

The linked issues pretty much says it all but to summarize, it would come in very handy, if you could control for which repositories an event (e.g. push) should trigger.
E.g. to have a workflow only executed in the main repo:

on:
  push:
    repositories:
      - 'quarkusio/quarkus'

E.g. to have a workflow only executed in forks (not the main repo):

on:
  push:
    ignore-repositories:
      - 'quarkusio/quarkus'

And to answer this question from @ethomson:

My understanding here is that you have some jobs that you want to run in forks and some jobs that you want to run in the main CI?

Exactly!

Cheers,
Falko

[ethomson]

Thanks for opening this here @famod - I've put this on our backlog.

[monim67]

Is there any progress on this issue?

[justinmayer]

@ethomson: Two suggestions to include in the backlog item for excluding forks from GitHub Actions:

1. Allow this configuration at the individual job level as well as for the entire workflow.
2. Support global exclusion of all forks without having to explicitly specify org+repository names. Following is an example individual job that would benefit from the previously-proposed ignore-forks: true syntax. This job is designed to publish new package releases (and thus should never run on any fork):

  deploy:
    ignore-forks: true
    name: Deploy
    environment: Deployment
    needs: [test, lint, docs]
    runs-on: ubuntu-latest
    if: github.ref=='refs/heads/main' && github.event_name!='pull_request'
    […]

[dpprdan]

Is this a repository filter - akin to the branches filter?

[0xangelo]

+1 for this, it would be really useful to us