WebGUI errors with Tagged blob objects

Summary

Part 1:

After tagging a git blob object and pushing it to gitlab.com the project page shows command line instructions like an empty repository but using one of the links from the

Otherwise you can start with adding a README, a LICENSE, or a .gitignore to this project.

text of that page results in a 404 error page.

Part 2:

After creating a normal commit the Tag is visible on the Repository/Tags web view. But several errors viewing the tag:

  • Tag has the comment "Cant find HEAD commit for this tag"
  • Clicking the download button fails (file not found)
  • Clicking delete tag results in a 500 error page (Whoops, something went wrong on our end.), but tag was deleted
  • On detailed view of the tag, clicking "Browse files" and "Browse commits" fail (404 Error page)

Steps to reproduce

On an empty repository:

Part 1:
echo "This is a blob" | git hash-object --stdin -w
git tag blob.txt $( echo "This is a blob" | git hash-object --stdin )
git push origin blob.txt
Part 2:
echo "This repository has a tagged blob object" > README.md
git add README.md
git commit -m "Added README.md"
git push -u origin master

Example Project

Part 1:

https://gitlab.com/lqb/tagged-blob1

Part 2:

https://gitlab.com/lqb/tagged-blob2

What is the current bug behavior?

The web GUI doesn't take care of tagged blob objects

What is the expected correct behavior?

Part 1:

Working README, LICENSE and .gitignore links on empty project page

Part 2:
  • Buttons that don't work with blob objects should be disabled
  • Maybe detect type (git cat-file -t blob.txt) and show it as tag comment