#6952 [Adjsut][v2] PR from fork repo without using a build CI image to check Pull request opened by SZL741023 Tracking issue Related to: (#6845) Why are the changes needed? In original work flow, if files

gen.Dockerfile

and

build-ci-image.yml

have been changed, the action for build ci image will be trigger. The action for check generation will be exercise after a new ci image is built. If the PR from fork repo, the ci image should not be rebuild. What changes were proposed in this pull request? In file

build-ci-image.yml

add the condition to check the PR is from the same repo or fork repo. If PR is from fork repo, build ci image will be skip. In file

check-generation.yml

add the condition to check the PR is from the same repo or fork repo. If PR is from fork repo, the action for check generation will be run in locally runner. Extract the tool versions from gen.Dockerfile to ensure that the correct version information is used. How was this patch tested? Ensure the PR from fork repo will not trigger the action for build ci image, and check generation will be run in locally runner. Labels Please add one or more of the following labels to categorize your PR: • added: For new features. • changed: For changes in existing functionality. • deprecated: For soon-to-be-removed features. • removed: For features being removed. • fixed: For any bug fixed. • security: In case of vulnerabilities This is important to improve the readability of release notes. Setup process Screenshots Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. Related PRs Docs link •

main

• #6583 • #6952 👈 flyteorg/flyte