Skip to content

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

Merged
starfy84 merged 1 commit intomasterfrom
add-catalog-info-yaml
Mar 25, 2026
Merged

chore: add catalog-info.yaml for Backstage developer portal#341
starfy84 merged 1 commit intomasterfrom
add-catalog-info-yaml

Conversation

@bitgo-backstage
Copy link
Copy Markdown
Contributor

@bitgo-backstage bitgo-backstage Bot commented Mar 22, 2026

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 has been set to other.

What you may want to update

Field Location Notes
spec.type catalog-info.yaml Currently set to 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

@bitgo-backstage bitgo-backstage Bot requested a review from a team as a code owner March 22, 2026 07:19
@bitgo-backstage bitgo-backstage Bot force-pushed the add-catalog-info-yaml branch from 1bb7331 to 7a24c67 Compare March 23, 2026 08:03
@bitgo-backstage bitgo-backstage Bot force-pushed the add-catalog-info-yaml branch from 7a24c67 to 432c648 Compare March 24, 2026 05:23
@starfy84 starfy84 merged commit 325f194 into master Mar 25, 2026
3 checks passed
@starfy84 starfy84 deleted the add-catalog-info-yaml branch March 25, 2026 15:05
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