Skip to content

chore: add catalog-info.yaml for Backstage developer portal#1

Open
bitgo-backstage[bot] wants to merge 1 commit into
masterfrom
add-catalog-info-yaml
Open

chore: add catalog-info.yaml for Backstage developer portal#1
bitgo-backstage[bot] wants to merge 1 commit into
masterfrom
add-catalog-info-yaml

Conversation

@bitgo-backstage

@bitgo-backstage bitgo-backstage Bot commented May 3, 2026

Copy link
Copy Markdown

Summary

This PR adds a catalog-info.yaml file for the Backstage developer portal.

The file was generated automatically by a scheduled sync across all BitGo repositories (VL-4315). The component type was inferred as other based on: no strong structural signal found.

What you may want to update

Field Location Notes
spec.type catalog-info.yaml Auto-detected as other. This should reflect the primary purpose of the repo. If this repo serves multiple roles (e.g. both a deployable service and a published library), pick the most significant one. Valid values: service, library, website, documentation, other. See the Backstage docs.
spec.owner catalog-info.yaml Set to the primary * owner from your CODEOWNERS file. Update if incorrect.
metadata.description catalog-info.yaml Optional — add a short description of what this repo does.

No other changes are made to your repository.

Questions? Reach out to Velocity on Slack.


Auto-generated by backfill-catalog-info.sh

@roshan-bitgo roshan-bitgo reopened this Jun 3, 2026
@bitgo-backstage bitgo-backstage Bot closed this Jun 3, 2026
@bitgo-backstage bitgo-backstage Bot reopened this Jun 3, 2026
@bitgo-backstage bitgo-backstage Bot enabled auto-merge June 3, 2026 11:51
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.

1 participant