Ensure file title wraps on merge conflict resolver screen

What does this MR do and why?

When a file that has a merge conflict has a very long path, the title does not currently wrap.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Before After
image image

How to set up and validate locally

  1. Check out this branch
  2. Create a new file with a long path in a project in the GDK with the Web IDE. For example, you can create a new file with the name src/components/experimental/duo/chat/components/duo_chat_context/duo_chat_context_item_selections/example_file_with_long_path_goes_here.md and the Web IDE will create the intermediate directories.
  3. Open an MR to add the file
  4. After the MR is open, use the Web IDE again from the master/main branch of the project to create the same file, but add different content to it. Do not create an MR, instead commit the file directly to the main/master branch.
  5. Return to the MR. You should see that there are conflicts. Click "Resolve" to view the merge conflict resolver.
    • Expected: you should see that the long path name of the file with a conflict wraps to a second line. This is in keeping with the styling that is applied to the file link on an MR diff file header.

Merge request reports

Loading