chore: add catalog-info.yaml for Backstage developer portal#74
Merged
OttoAllmendinger merged 1 commit intomasterfrom Mar 25, 2026
Merged
chore: add catalog-info.yaml for Backstage developer portal#74OttoAllmendinger merged 1 commit intomasterfrom
OttoAllmendinger merged 1 commit intomasterfrom
Conversation
bitgo-backstage
bot
force-pushed
the
add-catalog-info-yaml
branch
from
005abea to
5147357
Compare
bitgo-backstage
bot
force-pushed
the
add-catalog-info-yaml
branch
from
5147357 to
6b4f0a9
Compare
OttoAllmendinger
approved these changes
Mar 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a
catalog-info.yamlfile 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
spec.typecatalog-info.yamlother. 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.ownercatalog-info.yaml*owner from your CODEOWNERS file. Update if incorrect.metadata.descriptioncatalog-info.yamlNo other changes are made to your repository.
Questions? Reach out to Velocity on Slack.
Auto-generated by backfill-catalog-info.sh