Skip to content

fix(ci): run influxdb3-core tests when test harness changes#6811

Draft
Copilot wants to merge 3 commits intoclaude/add-codeblock-ci-tests-jRvG9from
copilot/sub-pr-6810
Draft

fix(ci): run influxdb3-core tests when test harness changes#6811
Copilot wants to merge 3 commits intoclaude/add-codeblock-ci-tests-jRvG9from
copilot/sub-pr-6810

Conversation

Copy link
Contributor

Copilot AI commented Feb 11, 2026

The workflow triggers on changes to test/**, Dockerfile.pytest, and compose.yaml but only checked for content changes, resulting in test harness modifications being skipped.

Changes:

  • Harness file detection: Check for changes to test/, Dockerfile.pytest, and compose.yaml using exact matches for root-level files
  • Test routing: When only harness files change, run influxdb3-core tests instead of skipping
  • Test command: Added test:codeblocks:influxdb3-core to package.json
  • CI setup: Added mock credentials for content/influxdb3/core/.env.test

Behavior:

# Before: harness changes trigger workflow but skip tests
CHANGED_FILES="" → should-run=false

# After: harness changes run influxdb3-core tests
CHANGED_HARNESS_FILES="test/pytest/conftest.py" → should-run=true, test-products=["influxdb3-core"]

Content changes continue to route to product-specific tests. When both content and harness files change, content-based routing takes precedence.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI and others added 2 commits February 11, 2026 12:25
Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com>
…ency

Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix CI workflow to handle harness file changes fix(ci): run influxdb3-core tests when test harness changes Feb 11, 2026
Copilot AI requested a review from jstirnaman February 11, 2026 12:28
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