Skip to content

When we merge catalogs using federation, be nice to see which repo the contents came from? #45

@boyney123

Description

@boyney123

Use Case

When we have many catalogs merged into one, some teams may be interested to see where the source of this information is from, so they can raise pull requests or issues on the content of the resource.

To give an example

Team 1 creates content, and is merged into main catalog for the org.
Team 2 see an issue with the content and want to raise a pull request, they have a link directly to do this on the UI vs trying to find it.

Proposed Solution

No response

Implementation Notes

No response

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.
  • If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions