## Overview This MVC epic represents a collection of issues for migrating the MR pipeline tab to GraphQL. ## Why is this important to the business? 1. Integration with new components like the recent pipeline mini-graph re-work will be easier in the future. 2. Increased performance in initial loading time as we could load data progressively - NOTE: This benefit dovetails with a theme from the ~FY25 engagement survey and ~"FY25::Q3" ~OKR [objective](https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/9166) to improve the internal developer experience. 3. With the page being optimal, it will allow features to be added and iterated on faster. 4. Data consistency between MR page and Pipelines tab ## Data analysis to support this prioritization Since each item in a `nodes` array increases complexity, loading a limited number of pipelines on first load, perhaps 5 would reduce load times significantly. Then, instead of having pages with controls (1,2,3,etc), implementing an infinite scroll would be where we can load 5 more whenever someone scrolls down. This has the huge benefit of loading a lot fewer pipelines on the first load and perhaps we never need to load more because 5 pipelines in MR is already enough information for most people. NOTE: Additional data analysis will be provided here once https://gitlab.com/gitlab-org/gitlab/-/issues/493433 is complete.