Merged
Conversation
Standardize on actions/checkout with fetch-depth 0 for versioning data. This avoids manual git fetch calls that can fail in container jobs with dubious ownership while keeping tag discovery intact.
Keep explicit tag refreshes for versioning jobs, but always mark the GitHub workspace as safe first so container jobs do not fail with dubious ownership errors.
pimlock
changed the title
drew
pushed a commit
that referenced
this pull request
Mar 16, 2026
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
1 participant
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.
Fixes https://github.com/NVIDIA/NemoClaw/actions/runs/22789880653/job/66114338702
Summary
git fetch --tags --forcesteps in versioning jobs$GITHUB_WORKSPACEas a safe Git directory before every manual tag fetchWhy
We want one consistent pattern for version discovery in CI: full checkout history, an explicit tag refresh, and a safe workspace configuration before any manual Git command. Some jobs already marked the workspace safe, but the containerized Docker build jobs did not, which caused
git fetch --tags --forceto fail with Git's dubious ownership protection. This change keeps the explicit tag fetches and standardizes the required safety setup everywhere they run.