Hi All,

I'd like to propose adopting ASF Infra's *fork-ci* action (
apache/infrastructure-actions/fork-ci) to save shared runner minutes and
cut down on clicking *"Approve and run"* for external PRs.
How it works

   -

   *Offloads WIP runs to forks:* Contributors run our CI workflow on their
   own public forks (using their own GitHub Actions quota) when they push
   commits.
   -

   *Mirrors results automatically:* A lightweight bridge + 15-minute cron
   sweep post the fork's run status (CI (fork)) directly onto the Fineract
   PR including links and failed job summaries even if the upstream workflow
   hasn't been approved yet.
   -

   *Safe for merging:* Since fork runs are untrusted, CI (fork) is *strictly
   informational* (the bridge never checks out PR code or touches secrets).
   Full, trusted upstream CI still gates every merge via merge_group /
   committer approval.

Rollout Plan

   1.

   *Phase 1 (Informational only):* Add fork-ci-signal.yml and
   fork-ci-status.yml to develop (pinned to a reviewed SHA) without
   skipping any existing upstream checks yet.
   2.

   *Phase 2 (Docs):* Add a quick note in our contributor guide on enabling
   GitHub Actions on forks (guide-url).
   3.

   *Phase 3 (Optimize):* Once verified alongside full merge_group
   validation, skip redundant heavy upstream jobs on initial external PR
   pushes.

Docs:
https://github.com/apache/infrastructure-actions/blob/main/fork-ci/README.md

Let me know what you think. if there are no objections, I'll file a JIRA
and open a PR for Phase 1.

Thanks,

Aman

Reply via email to