On Thu, Apr 15, 2021 at 10:48 AM Antoine Pitrou <anto...@python.org> wrote: > > > Le 15/04/2021 à 03:13, Kazuaki Ishizaki a écrit : > > As we know this is a common issue among Apache projects. While the > > projects do not have the final solution, Apache Spark project has a > > mechanism [1][2] to run a test in own local (forked) repository. Can we > > alleviate the problem a little bit? > > Anyone can already enable AppVeyor, Travis-CI and Github Actions on > their own fork. There is no particular action to do here.
There is a slight but meaningful difference. The fork is building the pull request's branch (refs/pull/<number>/head) whereas the pull request builds a reference created by github by merging the fork's branch to the pull request's base branch (refs/pull/<number>/merge). If we would merge based on the fork's CI status we may have issues on the main branch after the merge. This is what the spark pull request does, it merges [1] the pull request's branch with the pull request's base branch. [1]: https://github.com/apache/spark/pull/29504/files#diff-48c0ee97c53013d18d6bbae44648f7fab9af2e0bf5b0dc1ca761e18ec5c478f2R99 > > Regards > > Antoine.
