Avoid duplicate CI runs on non-fork Pull Requests

Question

Avoid duplicate CI runs on non-fork Pull Requests

dee-me-tree-or-love opened this issue 2 years ago · comments

What

For example in #435, the CI is triggered twice by push and pull_request triggers.
This should be avoided since it only adds confusion and possibly increases the total time for CI.

Example

Possible solutions

Configure the ci.yaml workflow to run on pushes only on tags or the master (soon main #420) branch, and always on pull requests. Example implementation as described here: How to trigger an action on push or pull request but not both? #26276