Repository navigation
ci: add SDK test workflow and path-filter backend CI - #32
Merged
Merged
Conversation
|
@MasRama is attempting to deploy a commit to the aadi's projects Team on Vercel. A member of the Team first needs to authorize it. |
aadityat23
reviewed
Jul 23, 2026
aadityat23
left a comment
Member
There was a problem hiding this comment.
Thanks for another great contribution! Really appreciate you taking the time to review the previous PR, identify the remaining scope, and improve the CI configuration instead of duplicating work. The path-filtering optimization and separate SDK workflow are nice additions. Merged! Looking forward to more contributions!
Contributor
Author
|
Thanks for the merge, @aadityat23! Happy to help. |
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.
Adds a separate GitHub Actions workflow for the SDK test suite and tightens the existing backend workflow so it only triggers on backend or workflow changes. Also adds CI status badges to the README.
PR #28 already migrated the backend tests to pytest and set up the initial workflow. This PR keeps that work and scopes it to
finverify-terminal/backend/**plus the workflow file itself.Closes #7
Local verification:
pytest -qinfinverify-terminal/backend: 189 passedpython -m tests.test_dvlinfinverify-terminal/sdk: 11 passedyaml.safe_load