feat(workflow): allow custom repos for OpenAPI freestyle task runs#4705
Open
Cynthia-0203 wants to merge 1 commit into
Open
feat(workflow): allow custom repos for OpenAPI freestyle task runs#4705Cynthia-0203 wants to merge 1 commit into
Cynthia-0203 wants to merge 1 commit into
Conversation
Signed-off-by: Cynthia <chenchen@koderover.com>
Cynthia-0203
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / Why we need it:
Allow OpenAPI-triggered freestyle workflow jobs to use the repository information provided in the request body.Previously, freestyle jobs could only update branch/PR/commit information for repositories already configured in the workflow. If users passed a different repository through OpenAPI, it would be filtered out.
What is changed and how it works?
For freestyle jobs, when repo_info is provided, the task now builds repository configs directly from the OpenAPI input, including code host, namespace, repository name, branch, PRs, commit, checkout path, submodules, and Perforce fields.
When repo_info is empty, the job still uses the repositories configured in the workflow.
Does this PR introduce a user-facing change?
This change is