Skip to content

Conversation

@rm3l
Copy link
Owner

@rm3l rm3l commented Oct 30, 2025

This pull request adds a Backstage entity metadata file
to this repository so that the component can
be added to the software catalog.
After this pull request is merged, the component will become available.
For more information, read an overview of the Backstage software catalog.
View the import job in your app here.

Summary by Sourcery

New Features:

  • Introduce Backstage entity metadata file (catalog-info.yaml) to enable importing the component into the software catalog

@sourcery-ai
Copy link

sourcery-ai bot commented Oct 30, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a Backstage catalog configuration file to register the gh-org-repo-sync component with the software catalog

Entity relationship diagram for Backstage catalog-info.yaml

erDiagram
  COMPONENT {
    string name
    string type
    string lifecycle
    string owner
    string github_project_slug
  }
  USER {
    string id
  }
  COMPONENT ||--|| USER : owner
Loading

File-Level Changes

Change Details Files
Introduce Backstage software catalog entity descriptor
  • Create new catalog-info.yaml file
  • Set apiVersion to backstage.io/v1alpha1 and kind to Component
  • Define metadata name and GitHub project annotation
  • Specify spec fields: type, lifecycle, and owner
catalog-info.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@rm3l
Copy link
Owner Author

rm3l commented Oct 30, 2025

Closing PR upon request for bulk import deletion. This request was created from Red Hat Developer Hub.

@rm3l rm3l closed this Oct 30, 2025
@rm3l rm3l deleted the backstage-integration branch October 30, 2025 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants