Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds comprehensive CI pipeline infrastructure for the new Tracker Service, including security scanning, license compliance checks, and updates to dependency management configuration. It also refactors the Coverity workflow logic for better handling of different event types.
Changes:
- Adds four new CI jobs to tracker-service.yaml: license-check (REUSE compliance), gitleaks-scan (secrets detection), bandit-scan (Python security), and trivy-scan (optional security scanning)
- Refactors coverity.yml to cleanly separate push-to-main events (comparing to parent commit) from other events (comparing to main branch)
- Updates dependabot.yml to include tracker paths in Docker, docker-compose, and pip ecosystem monitoring
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/tracker-service.yaml | Adds four security and compliance CI jobs for the tracker service |
| .github/workflows/coverity.yml | Refactors C/C++ file change detection logic with clearer conditional handling for push vs other events |
| .github/dependabot.yml | Adds tracker and tracker/test/service paths to Docker, docker-compose, and pip ecosystems |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
| contents: read | ||
|
|
||
| jobs: | ||
| detect-changes: |
There was a problem hiding this comment.
please explain what is the benefit of this change; previous approach was simpler and it did the same thing; what am I missing ?
There was a problem hiding this comment.
The benefit is to make this workflow required for PRs merging. Tests against Tracker will run as previously in case of changes to Tracker and workflow will not be blocking other PRs (without changes to Tracker).
📝 Description
This PR adds comprehensive CI pipeline infrastructure for the new Tracker Service, including security scanning, license compliance checks, and updates to dependency management configuration.
Changes:
✨ Type of Change
Select the type of change your PR introduces:
🧪 Testing Scenarios
Describe how the changes were tested and how reviewers can test them too:
✅ Checklist
Before submitting the PR, ensure the following: