CI update's
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
-
Add a GitHub Actions check to CI using
zizmor-
In this case, we need
# zizmor: ignore[unpinned-uses]for dtolnay/rust-toolchain@{nightly, stable, master, etc...) -
Pin all actions by commit (we can use: pinact, actions-up)
-
Add comments (similar to
// SAFETYin Rust) to potentially dangerous locations:
https://github.com/PyO3/pyo3/blob/126aa4422d514e9e51f3ed11e284735dc753762e/.github/workflows/cache-cleanup.yml#L2-L5
-
-
Use
uvinstead ofpip:
https://github.com/PyO3/pyo3/blob/126aa4422d514e9e51f3ed11e284735dc753762e/.github/workflows/build.yml#L60-L61
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 the existing files under .github/workflows, especially cache-cleanup.yml and the pip usage in build.yml. Run zizmor against the workflows and use its findings to track pinned actions, required ignores or safety comments, and the uv migration. Done means the CI check passes and all requested workflow updates are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100