Yicong-Huang commented on issue #4290: URL: https://github.com/apache/texera/issues/4290#issuecomment-4392664420
> I have been working on this task with the current CI. This is not a trivial problem. So far I have this setup: > > Three small workflows handle this: > > 1. In contributor fork: when a contributor push a branch, theiir fork automatically runs the full build and test suite. > 2. In the main repo, when you open a PR : a workflow looks across at the contributor fork, finds the matching build, and creates a status check called "Build" on the contributor PR that links to it. If something's wrong (fork has Actions disabled, > you pushed from a blocked branch like main, etc.), the check fails and explains why. > 3. In the main repo, every 5 minutes: a follow-up workflow updates the "Build" check as the contributor fork's run progresses, so the green checkmark / red X on the contributor PR matches what the contributor fork actually did. > > The "Build" check is required to merge, and its result mirrors the contributor fork's build result. Pass in the fork --> green check --> mergeable. Fail in the fork --> red X --> blocked. sounds good! do you have a link to a demo? e.g., workflow runs in your fork? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
