-
Bug
-
Resolution: Fixed
-
Low
-
4.14.1
-
None
-
None
-
Severity 3 - Minor
-
Summary
When trying to merge a forked repository back to the original repository, if a conflict is detected, the instructions given for the merge are incorrect.
Steps to Reproduce
- Fork a repository.
- Make changes to one file in the original repository after the fork.
- Make changes on the same file on the forked repository in order to create a conflict.
- Create a PR to merge back the Fork with the original repository
- After the PR gets created a warning panel shows the presence of a conflict and offers more information on how to solve the conflict.
Expected Results
The instructions show the correct steps to merge after the conflict is removed.
Actual Results
The instructions shown have an incorrect repository URL showed where the expected .git URL is shown as .undefined
Workaround
Apart from the repository URL, the instructions are still valid.
Execute the instructions being sure to replace .undefined with .git
I've opened a pull request to backport the fix to our 4.14 line. I'm not sure when/if a 4.14.6 release will happen, but if it does the fix for this will be included.
Best regards,
Bryan Turner
Atlassian Bitbucket