Update empty state when fetching error occurs in the Pipelines page
Summary
I had a connectivity problem when browsing the Pipelines page. GitLab then returned an empty state with an informative message, however, the empty state pattern being used does not meet our Pajamas guidelines.
Steps to reproduce
- Go to the Pipelines page.
- In my case, I had internet issues and the results in the list view failed to load.
Example Project
This happens on GitLab.com
What is the current bug behavior?
- Empty state does not meet the Pajamas guidelines.
What is the expected correct behavior?
- Empty state should meet the Pajamas guidelines.
-
There was an error fetching the pipelines
should be the title. -
Try again in a few moments or contact your support team
should be the text underneath.
https://design.gitlab.com/patterns/empty-states#example
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)