[PR #1090] [CLOSED] [WIP] Move test-sglang-integration job to standalone workflow file #2008

New issue

Closed

opened 2026-10-29 21:32:04 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-29 21:32:04 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/Mooncake/pull/1090
Author: @Copilot
Created: 11/20/2025
Status: ❌ Closed

Base: main ← Head: copilot/move-test-sglang-integration-job

📝 Commits (1)

78d99fd Initial plan

📄 Description

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Goal: Move the existing GitHub Actions job named test-sglang-integration out of its current workflow file and into a new standalone workflow file so it runs independently.

Tasks for the coding agent:

Search the repository for any workflow that defines a job called test-sglang-integration under .github/workflows/. Identify the file path(s) and capture the job definition and any workflow-level elements it relies on (on: triggers, env, permissions, concurrency, defaults, concurrency, workflow_call inputs if applicable, secrets, uses: actions/checkout or other reusable workflows, matrices, steps, container/services, runner requirements, caching steps).

Create a new workflow file at .github/workflows/test-sglang-integration.yml with:

name: "Test - sglang integration"

the same on: triggers as the original workflow (push, pull_request, workflow_dispatch, schedule) — preserve exactly what the original workflow used for this job, except if the original workflow used a matrix or other jobs; in that case include push and pull_request and workflow_dispatch to preserve manual runs.

the jobs: section should include only the test-sglang-integration job, copied verbatim including steps, env, uses, needs, services, strategy, concurrency, permissions, and any other attributes.

ensure any referenced actions, commands, or paths are correct and unchanged.

preserve required secrets and permissions. If the original workflow used repository-scoped defaults at top-level, replicate necessary permissions in the new workflow so the job continues to run successfully.

include a short comment header referencing that this file was moved from the original workflow and link to the original file path in the repository.

Modify the original workflow file to remove the test-sglang-integration job from its jobs: section. If removing the job leaves the original workflow with no jobs, delete the original workflow file instead.

Run a quick validation (yaml lint) on the new and modified workflow files to ensure syntactic validity.

Commit changes on a new branch named ci/move-sglang-integration-job with a descriptive commit message: "ci: move test-sglang-integration to separate workflow file".

Open a pull request titled: "[CI] move test-sglang-integration to its own workflow" with a description that explains what was changed and why (include references to the original PR #1089 if helpful) and list any noteworthy implications (e.g., different concurrency group, separate run history, different permissions if applicable).

Repository: kvcache-ai/Mooncake
Additional notes for the agent:

Keep the job contents identical where possible to avoid changing behavior.

If the original job referenced workflow-level environment variables or defaults, duplicate only the variables that the job actually needs.

If the job depends on artifacts produced by other jobs in the original workflow, detect that dependency: if it exists, preserve the dependency either by leaving the job in the original workflow or converting the other jobs into steps in the new workflow (prefer to leave dependent jobs in the original workflow and do not move unless safe). If such a dependency is detected, document it in the PR description and do not break the existing integration.

Make no other unrelated changes.

Please implement these changes and open the PR in the repository.

This pull request was created as a result of the following prompt from Copilot chat.

Goal: Move the existing GitHub Actions job named test-sglang-integration out of its current workflow file and into a new standalone workflow file so it runs independently.

Tasks for the coding agent:

Search the repository for any workflow that defines a job called test-sglang-integration under .github/workflows/. Identify the file path(s) and capture the job definition and any workflow-level elements it relies on (on: triggers, env, permissions, concurrency, defaults, concurrency, workflow_call inputs if applicable, secrets, uses: actions/checkout or other reusable workflows, matrices, steps, container/services, runner requirements, caching steps).

Create a new workflow file at .github/workflows/test-sglang-integration.yml with:

name: "Test - sglang integration"

the same on: triggers as the original workflow (push, pull_request, workflow_dispatch, schedule) — preserve exactly what the original workflow used for this job, except if the original workflow used a matrix or other jobs; in that case include push and pull_request and workflow_dispatch to preserve manual runs.

the jobs: section should include only the test-sglang-integration job, copied verbatim including steps, env, uses, needs, services, strategy, concurrency, permissions, and any other attributes.

ensure any referenced actions, commands, or paths are correct and unchanged.

preserve required secrets and permissions. If the original workflow used repository-scoped defaults at top-level, replicate necessary permissions in the new workflow so the job continues to run successfully.

include a short comment header referencing that this file was moved from the original workflow and link to the original file path in the repository.

Modify the original workflow file to remove the test-sglang-integration job from its jobs: section. If removing the job leaves the original workflow with no jobs, delete the original workflow file instead.

Run a quick validation (yaml lint) on the new and modified workflow files to ensure syntactic validity.

Commit changes on a new branch named ci/move-sglang-integration-job with a descriptive commit message: "ci: move test-sglang-integration to separate workflow file".

Open a pull request titled: "[CI] move test-sglang-integration to its own workflow" with a description that explains what was changed and why (include references to the original PR #1089 if helpful) and list any noteworthy implications (e.g., different concurrency group, separate run history, different permissions if applicable).

Repository: kvcache-ai/Mooncake
Additional notes for the agent:

Keep the job contents identical where possible to avoid changing behavior.

If the original job referenced workflow-level environment variables or defaults, duplicate only the variables that the job actually needs.

If the job depends on artifacts produced by other jobs in the original workflow, detect that dependency: if it exists, preserve the dependency either by leaving the job in the original workflow or converting the other jobs into steps in the new workflow (prefer to leave dependent jobs in the original workflow and do not move unless safe). If such a dependency is detected, document it in the PR description and do not break the existing integration.

Make no other unrelated changes.

Please implement these changes and open the PR in the repository.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/Mooncake/pull/1090 **Author:** [@Copilot](https://github.com/apps/copilot-swe-agent) **Created:** 11/20/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `copilot/move-test-sglang-integration-job` --- ### 📝 Commits (1) - [`78d99fd`](https://github.com/kvcache-ai/Mooncake/commit/78d99fda345a7fe93cdea329787b30fea7312656) Initial plan ### 📄 Description Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.  <details> <summary>Original prompt</summary> > Goal: Move the existing GitHub Actions job named `test-sglang-integration` out of its current workflow file and into a new standalone workflow file so it runs independently. > > Tasks for the coding agent: > 1. Search the repository for any workflow that defines a job called `test-sglang-integration` under `.github/workflows/`. Identify the file path(s) and capture the job definition and any workflow-level elements it relies on (on: triggers, env, permissions, concurrency, defaults, concurrency, workflow_call inputs if applicable, secrets, uses: actions/checkout or other reusable workflows, matrices, steps, container/services, runner requirements, caching steps). > 2. Create a new workflow file at `.github/workflows/test-sglang-integration.yml` with: > - name: "Test - sglang integration" > - the same `on:` triggers as the original workflow (push, pull_request, workflow_dispatch, schedule) — preserve exactly what the original workflow used for this job, except if the original workflow used a matrix or other jobs; in that case include push and pull_request and workflow_dispatch to preserve manual runs. > - the `jobs:` section should include only the `test-sglang-integration` job, copied verbatim including steps, env, uses, needs, services, strategy, concurrency, permissions, and any other attributes. > - ensure any referenced actions, commands, or paths are correct and unchanged. > - preserve required secrets and permissions. If the original workflow used repository-scoped defaults at top-level, replicate necessary permissions in the new workflow so the job continues to run successfully. > - include a short comment header referencing that this file was moved from the original workflow and link to the original file path in the repository. > 3. Modify the original workflow file to remove the `test-sglang-integration` job from its `jobs:` section. If removing the job leaves the original workflow with no jobs, delete the original workflow file instead. > 4. Run a quick validation (yaml lint) on the new and modified workflow files to ensure syntactic validity. > 5. Commit changes on a new branch named `ci/move-sglang-integration-job` with a descriptive commit message: "ci: move test-sglang-integration to separate workflow file". > 6. Open a pull request titled: "[CI] move test-sglang-integration to its own workflow" with a description that explains what was changed and why (include references to the original PR #1089 if helpful) and list any noteworthy implications (e.g., different concurrency group, separate run history, different permissions if applicable). > > Repository: kvcache-ai/Mooncake > Additional notes for the agent: > - Keep the job contents identical where possible to avoid changing behavior. > - If the original job referenced workflow-level environment variables or defaults, duplicate only the variables that the job actually needs. > - If the job depends on artifacts produced by other jobs in the original workflow, detect that dependency: if it exists, preserve the dependency either by leaving the job in the original workflow or converting the other jobs into steps in the new workflow (prefer to leave dependent jobs in the original workflow and do not move unless safe). If such a dependency is detected, document it in the PR description and do not break the existing integration. > - Make no other unrelated changes. > > Please implement these changes and open the PR in the repository. </details> *This pull request was created as a result of the following prompt from Copilot chat.* > Goal: Move the existing GitHub Actions job named `test-sglang-integration` out of its current workflow file and into a new standalone workflow file so it runs independently. > > Tasks for the coding agent: > 1. Search the repository for any workflow that defines a job called `test-sglang-integration` under `.github/workflows/`. Identify the file path(s) and capture the job definition and any workflow-level elements it relies on (on: triggers, env, permissions, concurrency, defaults, concurrency, workflow_call inputs if applicable, secrets, uses: actions/checkout or other reusable workflows, matrices, steps, container/services, runner requirements, caching steps). > 2. Create a new workflow file at `.github/workflows/test-sglang-integration.yml` with: > - name: "Test - sglang integration" > - the same `on:` triggers as the original workflow (push, pull_request, workflow_dispatch, schedule) — preserve exactly what the original workflow used for this job, except if the original workflow used a matrix or other jobs; in that case include push and pull_request and workflow_dispatch to preserve manual runs. > - the `jobs:` section should include only the `test-sglang-integration` job, copied verbatim including steps, env, uses, needs, services, strategy, concurrency, permissions, and any other attributes. > - ensure any referenced actions, commands, or paths are correct and unchanged. > - preserve required secrets and permissions. If the original workflow used repository-scoped defaults at top-level, replicate necessary permissions in the new workflow so the job continues to run successfully. > - include a short comment header referencing that this file was moved from the original workflow and link to the original file path in the repository. > 3. Modify the original workflow file to remove the `test-sglang-integration` job from its `jobs:` section. If removing the job leaves the original workflow with no jobs, delete the original workflow file instead. > 4. Run a quick validation (yaml lint) on the new and modified workflow files to ensure syntactic validity. > 5. Commit changes on a new branch named `ci/move-sglang-integration-job` with a descriptive commit message: "ci: move test-sglang-integration to separate workflow file". > 6. Open a pull request titled: "[CI] move test-sglang-integration to its own workflow" with a description that explains what was changed and why (include references to the original PR #1089 if helpful) and list any noteworthy implications (e.g., different concurrency group, separate run history, different permissions if applicable). > > Repository: kvcache-ai/Mooncake > Additional notes for the agent: > - Keep the job contents identical where possible to avoid changing behavior. > - If the original job referenced workflow-level environment variables or defaults, duplicate only the variables that the job actually needs. > - If the job depends on artifacts produced by other jobs in the original workflow, detect that dependency: if it exists, preserve the dependency either by leaving the job in the original workflow or converting the other jobs into steps in the new workflow (prefer to leave dependent jobs in the original workflow and do not move unless safe). If such a dependency is detected, document it in the PR description and do not break the existing integration. > - Make no other unrelated changes. > > Please implement these changes and open the PR in the repository.  --- ✨ Let Copilot coding agent [set things up for you](https://github.com/kvcache-ai/Mooncake/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-29 21:32:04 +00:00