Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.0.4
-
None
-
2
-
Severity 3 - Minor
-
1
-
Description
Links to commits on Commits and Overview tabs of the cross-repository Pull Request may lead to 404 error in some cases.
Steps to reproduce
No write access to the target repo
- Fork a repository you don't have write access to
- Clone the fork on your local machine
- Create a branch, create and push a commit(s)
- Create a Pull Request from that branch to `master` of origin repo
- Go to the Commits tab
- All commit links will result in 404 when clicked
- If you update the Pull Request with other commits, they will have broken links on both Commits and Overview tabs even if the entire page is reloaded unless you click on Diff tab
With write access to the target repo
- Repeat aforementioned steps until creating the Pull Request
- Create a PR to `master` of origin repo — you'll end up on Overview tab of Pull Request page, stay there
- Create and push another commit(s) to the source branch
- Click on Commits tab, but don't refresh entire page
- Last added commit links will result in 404 when clicked
- Same with the added commit links on Overview tab: they'll remain to be broken unless you click on Diff tab or reload entire page
Attachments
Issue Links
- is related to
-
BSERV-7090 Merge conflict message not shown on the overview tab to read only users
- Closed
-
BSERV-7293 401 Error received on Pull Request merge REST API when a conflict is met
- Closed