See which commits and pipelines are run in the fork project ref VS the parent project ref

Problem to solve

When #217451 (closed) is implemented it will be possible for project members (developer and up) to kick off a pipeline in the parent project based on the code of a forked project merge request.

This issue is scoped out of #217451 (closed) and intends to make it visible to see which commits and pipelines are run in the fork project ref VS the parent project ref. As we do not showcase these commits or pipelines differently in the merge request view.

In that view there is currently no indication of a ref they commits / pipelines are run on as it is assumed they will always run on the same ref (the merge request source branch).

Screenshot

Intended users

User experience goal

It should be easy to figure out if a pipeline has been run on the parent project or on the fork project.

Proposal

Acceptance criteria

• Pipelines run for a fork ref will receive a fork badge
• The badge is colored blue (info)
• The badge makes use of the new small badge component
• The fork badge will feature a tooltip with Pipeline ran in fork of project
• This badge will be propagated throughout any place pipeline badges are shown (pipeline table views, pipeline detail view info wells)

Mockup (browser made)
Mockups might differ, please check the acceptance criteria 🙏

Further details

This makes this issue closely related to #225497 (closed)

Permissions and Security

Documentation

Availability & Testing

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