Merge Requests links from the discussions - to see the specific diff doesn't works.
Summary
Merge Requests links from the discussions doesn't works.
on discussions - after the reviewer put his comments, when the code changed - it automatically resolved and there is a message that the comment resolved in "version XXX of the diff" and there is . a link to see the diff.
when you try to click on the link you receive 404 error
Steps to reproduce
- create repository
- create second branch
- make changes in the second branch
- open MR from the second branch into master
- add a comment on the change
- change something on the line that commented
- try to click on the link to the diff that provided on the comment - or on the link that on the end of the page "Compare with previous version"
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?
(What actually happens)
What is the expected correct behavior?
(What you should see instead)
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.)
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)