Gitlab GUI Improvements por XC-

A collection of improvements for GitLab's UI. Three features are included, with more planned.


Replaces GitLab's built-in project pipeline list with a view that offers filtering GitLab's UI does not:

• Search by pipeline name — partial, case-insensitive, multi-word matching. Also matches branch/ref, SHA, commit message and the user who triggered it.
• Status filtering — two compact dropdowns (Active / Finished); tick any combination of statuses (e.g. only Passed/Failed, or exclude Skipped pipelines). A single selected status is filtered on the server.
• Rich columns — stages shown as colored "balls" (mini pipeline graph; hovering a ball loads and shows its jobs, linking to the job pages), the commit message with the short SHA, and the user who triggered the pipeline.
• Pipeline actions — "Run pipeline" and the admin-only "Clear runner caches" are mirrored from the original view (shown only when GitLab's own buttons are present).
• Pagination — configurable page size (20/50/100 rows) with a windowed page pager. The rows-per-page choice is remembered across pages and browser sessions; the API is queried in batches of the same size for a fast initial load.

Replaces the project and group members page with a custom view:

• Search by name or username, applied server-side.
• Filtering — checkbox dropdowns for member source (direct / inherited / shared) and role.
• Ordering — by account, access granted, role and updated, both directions, all sorted server-side.
• Pagination — the same rows-per-page selector and pager as the pipeline list; members load incrementally, up to 10,000.

GitLab's own action buttons (import members, invite group, invite members) are mirrored into the panel header.


A new icon in GitLab's right-edge AI navigation rail (a distinctive orange "CC" badge) opens a sidebar listing the CI/CD catalog components published by the groups you belong to, with search and direct links to the catalog entries. GitLab's own catalog shows everything; this shows yours.

It works on gitlab.com and self-hosted GitLab instances, using the GraphQL API (/api/graphql, cursor-paginated) with an automatic fallback to the REST endpoints on older instances.

Licensed under MIT.