ci: use shallow checkout for tag-push releases#8544
Open
myleshorton wants to merge 2 commits intomainfrom
Open
ci: use shallow checkout for tag-push releases#8544myleshorton wants to merge 2 commits intomainfrom
myleshorton wants to merge 2 commits intomainfrom
Conversation
The set-metadata job was doing fetch-depth: 0 with fetch-tags for all trigger types, but tag-push releases only need version.sh validate (no git history needed). Full clone only needed for schedule/dispatch builds that call version.sh generate. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR optimizes the release workflow’s set-metadata job checkout behavior by using a shallow clone for tag-push releases, while keeping full-history checkout for scheduled/manual builds that generate versions.
Changes:
- Switch
actions/checkoutto conditionally usefetch-depth: 1forpush(tag) events andfetch-depth: 0otherwise. - Make
fetch-tagsconditional based on event type.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
version.sh validate calls get_latest_version which needs git tag -l to check the new version doesn't go backwards. Keep fetch-tags: true for all trigger types; only the commit history (fetch-depth) is conditionally shallow. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
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
fetch-depth: 1(shallow clone) instead offetch-depth: 0(full history) in theset-metadatajobversion.sh generate— tag pushes only callversion.sh validatewhich doesn't need git historyTest plan
set-metadatacheckout completes quicklyversion.sh generatestill works (full clone preserved for that path)🤖 Generated with Claude Code