Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 37,008
    • Issues 37,008
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,414
    • Merge requests 1,414
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #323154

Closed
Open
Created Mar 02, 2021 by Sarah Groff Hennigh-Palermo@sarahghp🔴Maintainer0 of 1 task completed0/1 task

Follow-up from "Collapse Deployments in Merge Request if Many"

The following discussion from !55239 (merged) should be addressed:

  • @sarahghp started a discussion: (+2 comments)

    This is a general thought and not meant to delay the MR: I find myself discontent with all the repetition here. I wonder how much of a pain it would be to create a deployments list component that we could pass just the deployments to and could abstract away all this repetition. How do you feel about this idea?

Assignee
Assign to
13.10
Milestone
13.10 (Past due)
Assign milestone
Time tracking