Fix 500 error on repos with no tags (#11870)
#11846 Introduced feature to show exact tag on commit view. However if a repo has no tags at all git prints out a separate and unhandled error " No names found, cannot describe anything." Adding --always to the command makes it always use the error in the style of "fatal: no tag exactly matches" even if there are no tags at all. Fixes #11869 Fixes #11868
This commit is contained in:
		
							parent
							
								
									bc4f7ba69b
								
							
						
					
					
						commit
						d729d685d0
					
				| @ -484,7 +484,7 @@ func (c *Commit) GetBranchName() (string, error) { | |||||||
| 
 | 
 | ||||||
| // GetTagName gets the current tag name for given commit
 | // GetTagName gets the current tag name for given commit
 | ||||||
| func (c *Commit) GetTagName() (string, error) { | func (c *Commit) GetTagName() (string, error) { | ||||||
| 	data, err := NewCommand("describe", "--exact-match", "--tags", c.ID.String()).RunInDir(c.repo.Path) | 	data, err := NewCommand("describe", "--exact-match", "--tags", "--always", c.ID.String()).RunInDir(c.repo.Path) | ||||||
| 	if err != nil { | 	if err != nil { | ||||||
| 		// handle special case where there is no tag for this commit
 | 		// handle special case where there is no tag for this commit
 | ||||||
| 		if strings.Contains(err.Error(), "no tag exactly matches") { | 		if strings.Contains(err.Error(), "no tag exactly matches") { | ||||||
|  | |||||||
		Loading…
	
		Reference in New Issue
	
	Block a user