ci: avoid duplicate PR checks and run full CDA tests nightly - #315
Merged
Conversation
Collaborator
Author
|
Dialing this back a bit from the python scripts, they're a bit much and would be hard to maintain. if for example someone wants to add a new doc extensions for doc deployment they might never think to go into a python script in the scripts directory to have this included. |
msweier
approved these changes
Sep 10, 2026
msweier
left a comment
Collaborator
There was a problem hiding this comment.
Cool! Maybe add a note to CONTRIBUTING.MD about gh workflow run CDA-testing.yml --ref <branch> so we remember to run it before approving something? Or if we want to check?
|
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
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.



Avoid duplicate tests on feature-branch pushes and move expensive CDA coverage to nightly/manual runs. Keep the existing standalone workflows, without a custom policy script, shared setup action, or aggregate merge gate.
3.x) for all PRs and pushes to main. Formatting and CodeQL run on PRs/main; superseded PR runs are cancelled.Validation: actionlint, configured YAML formatting, and whitespace checks pass. Parsed-workflow assertions verify standalone triggers, only Python 3.9/latest, and exactly 18 nightly CDA combinations. Python application code and dependencies are unchanged; the earlier local Python 3.9/3.14 mock tests and type checks passed. GitHub checks will validate the revised workflow head.
Tradeoff: CDA integration regressions may be found after merge. Maintainers can run
gh workflow run CDA-testing.yml --ref <branch>before merging when needed. Repository admins should require the two unit-test checks, formatting, CodeQL, and existing external checks; nightly CDA jobs must not be required on PRs. This PR does not change repository rules or publish a package.