When contributing to Caramel from a forked repository, for example working on an opened PR, I noticed that there are double CI builds happening: one in the AbstractMachinesLab / caramel repo, and one in my fork. This is confusing and it seems a bit wasteful.
This PR changes the CI configuration so that it runs on each commit only on the main branch or from opened pull requests, so there should not be duplicated CI workflows triggered from a forked repository in the most common contribution flow.
When contributing to Caramel from a forked repository, for example working on an opened PR, I noticed that there are double CI builds happening: one in the
AbstractMachinesLab / caramelrepo, and one in my fork. This is confusing and it seems a bit wasteful.This PR changes the CI configuration so that it runs on each commit only on the
mainbranch or from opened pull requests, so there should not be duplicated CI workflows triggered from a forked repository in the most common contribution flow.