Skip to content

[v2][Feat] Add the check-generate workflow can work in local runner for the PR from fork repo (#6845)#7040

Open
SZL741023 wants to merge 2 commits intoflyteorg:v2from
SZL741023:v2_git_workflows_dev
Open

[v2][Feat] Add the check-generate workflow can work in local runner for the PR from fork repo (#6845)#7040
SZL741023 wants to merge 2 commits intoflyteorg:v2from
SZL741023:v2_git_workflows_dev

Conversation

@SZL741023
Copy link
Copy Markdown
Contributor

@SZL741023 SZL741023 commented Mar 18, 2026

Tracking issue

Related to: (#6845)
Original PR: (#6952)

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 and the check generate will be run in local runner.

What changes were proposed in this pull request?

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.

check-generation.yml add the condition to check the PR is from fork repo or not, and add needs: [check-generate-conatiner, check-generate-local] to call these workflows with the check fork repo condition and monitor these workflow will be failure or not.
Add two workflows files check-generate-container.yml and check-generate-local.yml file and trigger by workflow call.
One does check generate in container, the other one does check generate in local runner.
Add the extract() function in check-generate-local.yml to 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

Adjust check-generate workflow that will call other workflows and check
other workflows will be failure or not
Separate original check-generate workflow to
check-generate-container.yml and rename to check-generate-container
Add new workflow file check-generate-local.yml for the PR from fork repo

Signed-off-by: SZL741023 <shengzhe.lin@icloud.com>
If the PR from fork repo, don't to rebuild the ci image

Signed-off-by: SZL741023 <shengzhe.lin@icloud.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant