Remove ?ref_type=heads in Gitlab file/dir link to reduce verbosity
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Maybe since mid Aug 2023, Gitlab links to file or directory now always has a query string parameter ?ref_type=heads. Example:
https://<myproject_path>/-/blob/master/.gitlab-ci.yml?ref_type=headsWe often paste the Gitlab URL in our Slack/Teams messages and internal documentation. The ?ref_type=heads parameter is just noise adding no value to the link.
Gitlab support had indicated that the ?ref_type=heads was added to address issue 20526 Impossible to browse a branch if a tag exists with the same name
Would it be possible to have a user/group config somewhere to disable the ?ref_type=heads workaround? As it never occurred to us to give an identical name to a branch and a tag. Also confirmed by a comment on that same issue 20526 that it might not be a good idea:
using branches and tags of the same name isn't a pattern that works well. If you do the same thing locally, you'll end up with warnings like
warning: refname 'v0.0.1' is ambiguous
On github, there is no equivalent of ?ref_type=heads.