openvinotoolkit / openvinotoolkit/physicalai
Epic: CI Validation
Open
Nobody has claimed this yet.
CI
epic
- Dominant language
- Python
- Stars
- 28
- Forks
- 22
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 30
Description
Summary
Add CI workflows for code, package, and docs validation.
Scope
Add lint, type-check, unit test, package build, and docs validation workflows.
Status
Planned
Dependencies
#22
Related Issues
- #22 Test Matrix and Hardware Isolation
- #29 Docs Quality Gates
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing dependency issue #22 and related issue #29 to understand the test-matrix, hardware-isolation, and docs requirements. Define the CI workflow entry points for linting, type checks, unit tests, package builds, and documentation validation; done means each listed validation runs in CI with the required dependencies covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, documentation, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100