<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary I used the following API resource <https://docs.gitlab.com/ee/api/commits.html#get-references-a-commit-is-pushed-to> to list all tags associated to a certain commit. It showed that this API also lists tags for unrelated commits, as shown in my demo repository. From the documentation I assumed that this resoucrce works like `git tag --points-at <commit-sha>`, which it didn't. we have an internal deployment tool that tries to resolve a tag to a certain commit, if it exists. Lets say I deploy `serviceX` in revision `c15cbf97d1d0f82b90ff1e44b61071e8a89eae39` it tries to determine the tag that is assigned to this commit, e.g. `v1.2.3`. This works perfectly fine using `git tag --points-at c15cbf97d1d0f82b90ff1e44b61071e8a89eae39` but requires to have the git repository context on the machine running the deploy tool, which would not be required if I could retrieve this information easily from the Gitlab API. ### Steps to reproduce I created a minimal example that demonstrates the issue: <https://gitlab.com/klingtnet/commit-refs-bug-demo>. <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> <https://gitlab.com/klingtnet/commit-refs-bug-demo> ### What is the current *bug* behavior? <!-- Describe what actually happens. --> Tags are shown for untagged commits. ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> Tags are only shown as references if the commit is actually tagged. ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> :x: ### Output of checks <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com --> :x: #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> The demo repository uses the current gitlab.com API. <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check :x: <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->