CI: shrink checkouts via shallow / treeless partial clones#2177
Merged
Conversation
Of the 15 workflow checkouts that used fetch-depth: 0, only 7 actually need the commit graph (setuptools-scm, git merge-base, git worktree), and none of them need historical blobs. The remaining 8 either do no git operations or only need tag resolution. - 6 sites with no local git ops: fetch-depth: 1 (ci.yml ci-vars, build-docs.yml, release-upload.yml, release.yml check-tag, release-cuda-pathfinder.yml upload-assets, coverage.yml coverage-windows) - 2 sites that resolve a tag to a SHA via lookup-run-id: fetch-depth: 1 + fetch-tags: true (release.yml determine-run-id, release-cuda-pathfinder.yml prepare) - 7 sites that need the commit graph but not blobs: fetch-depth: 0 + filter: blob:none (build-wheel.yml, ci.yml detect-changes, cleanup-pr-previews.yml, coverage.yml coverage-linux, coverage.yml build-wheel-windows, test-sdist-linux.yml, test-sdist-windows.yml) Closes NVIDIA#2091
Contributor
Member
Author
|
/ok to test e673fe1 |
|
Member
Author
|
CI is fully green, and the checkout-step speedup is significant. Sampling representative jobs from this PR's run (
Every checkout is now seconds rather than minutes. Cumulative compute time saved per CI run across the full matrix (6 linux-64 + 6 linux-aarch64 + 6 win-64 builds, 2 sdist jobs, No correctness issues observed: -- Leo's bot |
Member
Author
|
Thanks, Mike! |
github-actions Bot
pushed a commit
that referenced
this pull request
Jun 9, 2026
Removed preview folders for the following PRs: - PR #2177
rwgk
added a commit
that referenced
this pull request
Jun 12, 2026
PR #2177 made the release workflow checkout shallow, so the dry-run tag validation now needs tags fetched explicitly while keeping history shallow.
rwgk
added a commit
that referenced
this pull request
Jun 13, 2026
* Check release notes for planned backports Require mainline cuda-bindings and cuda-python releases to explicitly declare a planned backport tag or mark it not planned. Keep actual backport releases unblocked while surfacing missing notes as warnings, and preserve docs builds for older tags that still use ci/versions.json. * Add dry-run release workflow mode Validate release docs, archives, and wheels without publishing to GitHub Releases, GitHub Pages, TestPyPI, or PyPI. * Allow dry-run docs branch deployment Add an explicit dry-run docs branch input so release dry-runs can optionally write generated docs to a seeded non-production branch while keeping artifact-only dry-runs as the default. * Default release workflow dispatches to dry-run Make dry-run the first and default release action so production publishing must be deliberately selected for manual release workflow runs. * Constrain dry-run docs deploy branches Require optional dry-run docs deployments to target a non-production gh-pages-* branch so manual release dry-runs cannot accidentally publish docs to production or source branches. * CI: fetch tags for release dry-run validation PR #2177 made the release workflow checkout shallow, so the dry-run tag validation now needs tags fetched explicitly while keeping history shallow. * CI: document release dry-run retest matrix Add workflow-local guidance for validating non-trivial release workflow changes with focused dry-run coverage.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #2091.
15 workflow checkouts used
fetch-depth: 0(full clone with every blob in history). The audit in #2091 showed only 7 actually need the commit graph (setuptools-scm,git merge-base,git worktree), and none need historical blobs. The remaining 8 either do no local git operations or only need tag resolution. This PR applies the three patterns from that audit.Patterns applied
Plain shallow clone —
fetch-depth: 1(6 sites, no local git ops)ci.ymlci-varsbuild-docs.ymlrelease-upload.ymlrelease.ymlcheck-tagrelease-cuda-pathfinder.ymlupload-assetscoverage.ymlcoverage-windowsShallow + tags —
fetch-depth: 1+fetch-tags: true(2 sites,lookup-run-iddoesgit rev-parse <tag>)release.ymldetermine-run-idrelease-cuda-pathfinder.ymlprepareTreeless —
fetch-depth: 0+filter: blob:none(7 sites, commit graph needed but not historical blobs)build-wheel.yml(setuptools-scm)ci.ymldetect-changes (git merge-base+git diff --name-only)cleanup-pr-previews.yml(git worktree add gh-pages)coverage.ymlcoverage-linux (setuptools-scm)coverage.ymlbuild-wheel-windows (setuptools-scm)test-sdist-linux.yml(python -m build→ setuptools-scm)test-sdist-windows.yml(same)Should noticeably reduce checkout time, especially on Windows where git operations are slower.
Test plan
release.ymlandrelease-cuda-pathfinder.ymlpaths (these aren't triggered by PR CI)-- Leo's bot