Skip to content

Skip duplicate builds after CI-only merges - #115

Merged
gouyt13 merged 1 commit into
mainfrom
ci/skip-duplicate-main-ci
Sep 25, 2026
Merged

gouyt13 merged 1 commit into
mainfrom
ci/skip-duplicate-main-ci

Conversation

@gouyt13

@gouyt13 gouyt13 commented Sep 25, 2026

Copy link
Copy Markdown
Member

Summary

The CI routing update in #114 correctly selected every check on the PR, but selected them again on its merge push to main. The second run repeated C++ platform builds, sanitizers, and Python package builds even though the merge changed only routing files and Markdown.

This change keeps broad validation for routing PRs. On a tagged main version, a push containing only the routing files and Markdown selects Python quality, which runs the selector tests, without repeating platform builds. Mixed source changes and untagged versions retain full selection; the latter preserves the automatic release gate.

Verification

  • 22 CI and release unit tests passed
  • Ruff formatting and linting passed for .github/scripts
  • ./scripts/check-python.sh passed using the project environment's Ruff
  • Replayed the Run CI checks only for affected files #114 merge diff: selected checks changed from all groups to python_quality
  • git diff --check passed

@gouyt13
gouyt13 merged commit a010649 into main Sep 25, 2026
22 checks passed
@gouyt13
gouyt13 deleted the ci/skip-duplicate-main-ci branch September 25, 2026 05:07
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