Referenced commit shas won't be converted to links on the Tags page
Summary
On the Tags
page, when seeing a Release Tag that has a link to a specific commit sha on the release notes section, the referenced commit sha's won't be converted to links (blue anchor), and instead is being displayed the same color as the body text.
Steps to reproduce
- Create a release using GitLab's UI
- Add a link to a commit sha to the release notes text area
- Create the release
- Go to Tags, and look for the release Tag
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)
What is the current bug behavior?
Commit SHA on the release notes are not styled correctly (body text color).
What is the expected correct behavior?
Commit SHA on the release notes should be styled as anchor (blue text).
Relevant logs and/or screenshots
When creating a tag with release notes which references a commit sha, inside the Release page these links get properly created:
But not on the Tags page:
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(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`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(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)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)