New merge request: change empty state
What does this MR do and why?
Changes the empty state of «New merge request» if there aren't any commits/changes.
Reported by @jmiocene via #394879 (comment 1323829787)
Screenshots or screen recordings
| Before | After | After with commits |
|---|---|---|
 |
 |
 |
How to set up and validate locally
- Empty MR: http://gdk.test:3000/flightjs/Flight/-/merge_requests/new?merge_request%5Bsource_project_id%5D=6&merge_request%5Bsource_branch%5D=3-test-branch&merge_request%5Btarget_project_id%5D=6&merge_request%5Btarget_branch%5D=master
- MR with commits: http://gdk.test:3000/flightjs/Flight/-/merge_requests/new?merge_request%5Bsource_project_id%5D=6&merge_request%5Bsource_branch%5D=immutable_attributes&merge_request%5Btarget_project_id%5D=6&merge_request%5Btarget_branch%5D=master
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.
Edited by Sascha Eggenberger