Repository navigation
ci: discuss a lightweight Python smoke check for pull requests #632
Description
Problem
AssetOpsBench currently runs security checks on pull requests but does not automatically validate Python tests or dependency consistency.
Proposal
Introduce a lightweight GitHub Actions workflow that:
- Runs a small set of tests without external services:
uv run --frozen pytest src/llm/tests src/servers/utilities/tests -q - Validates dependency consistency using
uv lock --check. - Runs only when Python source files or dependency configurations change.
- Respects IBM's GitHub Actions restrictions and avoids heavy integration tests.
Benefits: Detect regressions earlier, improve code quality, and reduce manual testing during PR reviews.
Maintainer Feedback
Before implementation, I would appreciate guidance on:
- Is this lightweight CI approach suitable?
- Should checks be required or informational?
- Which Python/uv installation method is preferred under IBM's GitHub Actions policy?
No workflow changes have been made yet. I can implement a focused PR once the preferred approach is confirmed.
Metadata
Metadata
Assignees
Labels
No labels
Activity
docs(roadmap): track CI discussion issue IBM#632
DhavalRepo18 commentedon Oct 14, 2026
@yousseffaouzi, we had those but did not operationalize them. Try one.
yousseffaouzi commentedon Oct 14, 2026
Thanks, @DhavalRepo18 . I’ll start with one small PR-focused Python smoke workflow and keep it intentionally narrow: read-only permissions, path filters, lockfile consistency, and only service-independent tests.
I’ll avoid making it a required gate or adding external-service/credential-dependent tests. I’ll share the first version as a focused PR for review.
DhavalRepo18 commentedon Oct 16, 2026
@yousseffaouzi Please see the git issue; we will handle this PR post refresh of the main branch.
yousseffaouzi commentedon Oct 16, 2026
Thanks, @DhavalRepo18
Understood, I’ll leave #636 unchanged for now and wait for the main-branch refresh in #644.
Once the refreshed main is available, I’ll re-check the workflow against it and update the PR only if needed.