On Sun, 2021-01-10 at 21:19 +0000, Javier Jardón wrote: > On 2021-01-10 09:28, Tristan Van Berkom wrote: > > [...] > > This was fixed by running CI on our repo on the `pull_request` event, > > which will be triggered in our repo whenever a pull request is created > > even if it is created from a downstream fork. > > > > It is a well known issue that running CI on both "push" events and > > "pull_request" events causes CI to run twice, which is wasteful, > > however we do want the ability to run CI in advance of creating a pull > > request. > > > > While github has yet to provide a solution for this issue, I was able > > to find this workaround[3], testing so far shows this is working as > > expected. > > This doesn't seem to work on this PR (generated from a fork, rebased > against current master): [1]
Indeed, this PR also does not run the actions for a pull request originating from a forked repo: https://github.com/apache/buildstream/pull/1440 Even though it is working well on the testbed: https://github.com/buildstream-migration/buildstream/pull/13 This appears to be more restrictions from the apache namespace on github. /me bangs head on desk. Cheers, -Tristan
