Skip to content

Python: Add GitHub Copilot integration tests to CI workflows#6345

Closed
giles17 wants to merge 1 commit into
microsoft:mainfrom
giles17:ghcp-integration-tests-ci
Closed

Python: Add GitHub Copilot integration tests to CI workflows#6345
giles17 wants to merge 1 commit into
microsoft:mainfrom
giles17:ghcp-integration-tests-ci

Conversation

@giles17
Copy link
Copy Markdown
Contributor

@giles17 giles17 commented Jun 4, 2026

Changes

Adds a dedicated GitHub Copilot integration test job to the Python CI workflows, matching the pattern used by other provider integration tests (OpenAI, Foundry, Cosmos, etc.).

What's added

A python-tests-github-copilot job in both:

  • python-integration-tests.yml (called from manual integration test orchestrator)
  • python-merge-tests.yml (merge queue + daily schedule)

Job details

  • Runs the 6 integration tests in packages/github_copilot/tests marked with @pytest.mark.integration
  • Uses COPILOT_GITHUB_TOKEN secret from the integration environment (same secret used by sample validation)
  • Includes path filtering in merge-tests: only triggers on packages/github_copilot/** or core changes
  • Added to needs lists in both the trend report and status-check jobs

Test coverage (from PR #6292)

  1. Basic non-streaming response
  2. Streaming response
  3. Function tool invocation
  4. Session context (multi-turn)
  5. Session resume by ID
  6. Shell command execution

Prerequisites

  • COPILOT_GITHUB_TOKEN secret must exist in the integration environment (already configured for sample validation)

Add a dedicated integration test job for the github_copilot package to both
python-integration-tests.yml and python-merge-tests.yml.

The job:
- Runs 6 integration tests (basic, streaming, tools, session, resume, shell)
- Uses COPILOT_GITHUB_TOKEN secret from the integration environment
- Follows the same pattern as other provider integration jobs (OpenAI, Foundry, etc.)
- Includes path filtering in merge-tests (github_copilot package + core changes)
- Added to needs lists in report and check jobs

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 4, 2026 17:26
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a dedicated GitHub Copilot provider integration-test job to the Python CI workflows, aligning with the existing pattern used for other provider integration tests (OpenAI, Foundry, Cosmos, etc.). This ensures Copilot-specific integration coverage is exercised in both the manual integration workflow and merge/scheduled CI runs while remaining gated by path filters.

Changes:

  • Adds a python-tests-github-copilot job to python-merge-tests.yml, including paths-filter gating and inclusion in the report + status-check needs lists.
  • Adds a matching python-tests-github-copilot job to python-integration-tests.yml and wires it into the report + status-check aggregation.
  • Extends the merge-tests paths-filter to track python/packages/github_copilot/** changes.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/python-merge-tests.yml Adds a Copilot integration-test job with merge-queue path gating and includes it in reporting/check aggregation.
.github/workflows/python-integration-tests.yml Adds a Copilot integration-test job to the manually-orchestrated integration workflow and includes it in reporting/check aggregation.

Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated Code Review

Reviewers: 4 | Confidence: 93% | Result: All clear

Reviewed: Correctness, Security Reliability, Test Coverage, Design Approach


Automated review by giles17's agents

@giles17 giles17 closed this Jun 4, 2026
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.

2 participants