Hi all, As of today (apache/datafusion-comet#7311), CI for a Comet pull request from a fork into main runs on the contributor's fork, not on the ASF's shared GitHub runners. This is the same setup apache/datafusion and apache/arrow-rs already use, and it reduces the load Comet puts on the shared ASF runner capacity. The required checks and the merge queue still run in apache/datafusion-comet, and the queue still tests every change merged with main before it lands.
If you have an open pull request from a fork, you may see a failing check named "CI (fork)" that says "Enable CI on your fork". That means GitHub Actions is turned off on your fork, which is GitHub's default for new forks. The check does not block merging, but it means the PR tests have not run, so reviewers have no CI results to go on. To fix it: 1. Open your fork's Actions tab and enable workflows. 2. Sync your fork's main with apache/datafusion-comet, then merge or rebase it into your branch. 3. Push your branch. A "Comet CI (fork run)" starts in your fork, and the check on the pull request follows it within a few minutes. Pull requests opened before the change already have their earlier CI results, but they also need this before their next push. The details are in this contributor guide update: https://github.com/apache/datafusion-comet/pull/7352 If you can't enable Actions on your fork, please say so on your pull request and a maintainer will help. Thanks, Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
