Fixes a bug where sometimes the widget state would be empty
What does this MR do and why?
Sometimes when creating a new merge request the merge widget will display an empty state component whilst we wait for requests to complete and for the merge status to be checked. This changes that empty state component by always falling back to the checking
state component.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.