Generic Pipeline Message in the Merge Request

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Release notes

GitLab makes it easy for you and your teams to collaborate while creating software. In doing so we make the Merge Request central to that collaboration by including built in CI/CD. You can see results from your CI/CD pipelines directly in your merge request for common tasks like Security Scanning, Code Quality and even Infrastructure as Code output. Starting this release you can now provide generic Merge Request feedback reports directly into the merge request to enable easier collaboration with your team.

Problem to solve

Options for displaying generic job output in text form is difficult and users often resort to API calls to post comments on the merge request instead of providing messages directly in the Merge Request.

Intended users

User experience goal

Proposal

Dogfooding - replace our use of Danger-Review job to post Messages and Warnings (example) with a Generic Report in the MR header (not as a comment).

Could use some adjusted form of expose_as

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by 🤖 GitLab Bot 🤖