1086 optimize ci workflows - #1135
Conversation
|
Warning Review limit reached
Next review available in: 15 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe CI environment actions now use updated checkout and uv setup actions. The publish workflow removes separate test jobs and conditional publishing. The coverage workflow removes its job-level ChangesCI workflow updates
Estimated code review effort: 2 (Simple) | ~15 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/setup-env-notebooks/action.yml:
- Around line 14-18: Update the “Install uv” step in the setup-env-notebooks
action to pass the action’s declared python-version input to astral-sh/setup-uv,
ensuring uv sync --group notebook uses the selected matrix Python version.
Preserve the existing version and cache settings.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 7d4a919a-2538-487a-9a61-f9fbea8d7e8c
📒 Files selected for processing (5)
.github/setup-env-notebooks/action.yml.github/setup-env/action.yml.github/workflows/build_and_publish.yml.github/workflows/check_notebooks.yml.github/workflows/coverage.yml
💤 Files with no reviewable changes (2)
- .github/workflows/coverage.yml
- .github/workflows/check_notebooks.yml
There was a problem hiding this comment.
Pull request overview
This PR optimizes HSSM’s CI workflows by removing legacy BLAS/LAPACK-related configuration, simplifying environment setup to rely on uv, and streamlining the publish workflow.
Changes:
- Removed
PYTENSOR_FLAGSBLAS/LAPACK configuration from selected workflows and dropped OS-level BLAS/LAPACK installation from reusable composite actions. - Updated reusable composite actions to rely on
astral-sh/setup-uvfor Python provisioning instead ofactions/setup-python. - Simplified the release publish workflow by removing the pre-publish full test-suite job and related
workflow_dispatchinput.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/coverage.yml | Removes job-level BLAS/LAPACK env configuration for coverage runs. |
| .github/workflows/check_notebooks.yml | Removes job-level BLAS/LAPACK env configuration for notebook execution. |
| .github/workflows/build_and_publish.yml | Removes optional/required full test-suite job before publishing releases. |
| .github/setup-env/action.yml | Simplifies env setup by relying on setup-uv (and updates action versions). |
| .github/setup-env-notebooks/action.yml | Simplifies notebook env setup by relying on setup-uv (and updates action versions). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cpaniaguam
left a comment
cpaniaguam
left a comment
There was a problem hiding this comment.
lgtm. Consider adding the python version to the install uv action for reproducibility.
With the job-level PYTENSOR_FLAGS removed, `${{ env.PYTENSOR_FLAGS }}`
expanded to an empty string and exported PYTENSOR_FLAGS=, blanking
PyTensor's defaults instead of leaving them alone. run_tests.yml still
sets an explicit value where the BLAS flags are needed.
Refs #1086
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
@codex review |
Fixed |
Some immediate improvements to our ci workflows
Summary by CodeRabbit