Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,331
    • Merge requests 1,331
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #327634
Closed
Open
Issue created Apr 13, 2021 by Austin Regnery@aregnery🔴Developer

Display Status checks as a non-blocking Merge Request Widget

This is a frontend implementation issue

Problem to solve

APIs that are listed as a status to check should appear within a Merge Request. This is non-blocking information that provides better context to the systems that tie to a change.

Proposal

Add Status checks after Test summary in the MR Widget container.

Design

For the first iteration, they backend will only return the status as pending | approved. Thus we won't be showing failure icons for now.

Passed (Collapsed) Passed__Expand_

Pending (Expanded) Pending__Collapse_

Is this a cross-stage feature?

🤝 groupcompliance groupsource code groupcode review

Licensing

GitLab Ultimate

Implementation

Estimate weight of 3️⃣ for the frontend, because while the component itself is relatively simple, it needs to be integrated into the merge request widget space which is quite complex.

  1. Create a new status checks MR widget using the ReportSection component.
  2. Fetch the status checks added in !61300 (merged).
  3. Create a status checks issue body using the SummaryRow to display each status.
  4. If any checks are still not completed, we should continue to poll and update the component once the checks have completed.
  5. Add feature specs.
Edited May 26, 2021 by Austin Regnery
Assignee
Assign to
Time tracking