tools/git: use --always with git describe#4286
Open
anirudhrb wants to merge 1 commit intomicrosoft:mainfrom
Open
tools/git: use --always with git describe#4286anirudhrb wants to merge 1 commit intomicrosoft:mainfrom
anirudhrb wants to merge 1 commit intomicrosoft:mainfrom
Conversation
If the repository doesn't have tags, git describe fails with: fatal: No names found, cannot describe anything. From the official git documentation: --always Show uniquely abbreviated commit object as fallback. This makes our `git describe` command more robust and prevents exceptions in cases where there are no tags to describe the commit. It is possible that some forked (i.e. not upstream) repositories don't have tags. In these cases, instead of failing, fallback to commit id. Signed-off-by: Anirudh Rayabharam <anrayabh@microsoft.com>
pupacha
approved these changes
Feb 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
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.
If the repository doesn't have tags, git describe fails with:
fatal: No names found, cannot describe anything.
From the official git documentation:
--always
Show uniquely abbreviated commit object as fallback.
This makes our
git describecommand more robust and prevents exceptions in cases where there are no tags to describe the commit. It is possible that some forked (i.e. not upstream) repositories don't have tags. In these cases, instead of failing, fallback to commit id.