ci: Update ci #15
ci: Update ci #15
Conversation
Signed-off-by: Hubert Cymerys <hubert.cymerys@intel.com>
There was a problem hiding this comment.
Pull Request Overview
This PR updates the CI/CD configuration by consolidating workflow definitions and migrating to reusable workflows from the intel/mfd repository. The changes centralize workflow logic, simplify maintenance, and remove redundant workflow files.
Key changes:
- Migrated workflows to use reusable workflows from
intel/mfd/.github/workflows/ - Added new workflow files for code standards, dependency review, and PR validation
- Removed the local
build_upload_whl.ymlandcodeql.ymlimplementations
Reviewed Changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/run_tests.yml |
New workflow for running unit and functional tests using centralized workflow |
.github/workflows/pull_requests.yml |
Simplified repository name reference by removing fallback logic |
.github/workflows/manual_release.yml |
Updated to use centralized release workflow with simplified matrix configuration |
.github/workflows/main.yml |
New workflow for CI builds on main branch using centralized workflow |
.github/workflows/dependency_review.yml |
New workflow for automated dependency review |
.github/workflows/codeql.yml |
Removed local CodeQL implementation (likely moved to centralized workflow) |
.github/workflows/check_pr_format.yml |
New workflow for validating PR titles and commits |
.github/workflows/check_code_standard.yml |
New workflow for code standard validation |
.github/workflows/build_upload_whl.yml |
Removed local build workflow implementation (moved to centralized workflow) |
.github/dependency_review.yml |
Configuration file for dependency review settings |
.github/dependabot.yml |
Configuration for automated dependency updates |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| release_steps: true | ||
| - python_version: '3.13' | ||
| release_steps: false |
There was a problem hiding this comment.
The release_steps configuration appears counterintuitive - Python 3.10 is set to perform release steps while Python 3.13 is not. Typically, the latest/newest Python version would be used for release operations. Consider verifying this configuration is intentional, or swap the boolean values if the newer Python version should handle releases.
| release_steps: true | |
| - python_version: '3.13' | |
| release_steps: false | |
| release_steps: false | |
| - python_version: '3.13' | |
| release_steps: true |
No description provided.