Adopt Backstage catalog-info.yaml as a repo metadata source #49

New issue

Closed

opened 2026-05-23 20:55:27 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-23 20:55:27 +00:00

Owner

Originally filed by @coilysiren on 2026-05-12T07:50:44Z - https://github.com/coilysiren/repo-recall/issues/87

Parse catalog-info.yaml (Backstage software-catalog schema) when present at repo root. Use it to populate owner, type, system, and dependency-graph edges in repo-recall's index.

Why

Backstage shops already maintain this file. Adopting the schema means repo-recall can light up on day one against any Backstage-adjacent codebase, with zero new authoring burden on the user.
Gives us a free dependency graph between repos without inventing our own format.
Even non-Backstage users get a familiar, documented schema to opt into.

Scope

Parser for the subset of fields we care about: kind, metadata.name, spec.owner, spec.type, spec.system, spec.dependsOn.
Surface in the dashboard: owner badge, type filter, dependency edges between indexed repos.
Ignore unknown fields, do not validate the full Backstage schema.

Out of scope

Authoring/scaffolding the file.
TechDocs, Scorecards, or any other Backstage surface (separate issues).
Bidirectional sync with a running Backstage instance.

Cross-ref: discussion comparing repo-recall to Backstage, decided to cherry-pick features rather than ship a Backstage plugin.

_Originally filed by @coilysiren on 2026-05-12T07:50:44Z - [https://github.com/coilysiren/repo-recall/issues/87](https://github.com/coilysiren/repo-recall/issues/87)_ Parse `catalog-info.yaml` (Backstage software-catalog schema) when present at repo root. Use it to populate owner, type, system, and dependency-graph edges in repo-recall's index. ## Why - Backstage shops already maintain this file. Adopting the schema means repo-recall can light up on day one against any Backstage-adjacent codebase, with zero new authoring burden on the user. - Gives us a free dependency graph between repos without inventing our own format. - Even non-Backstage users get a familiar, documented schema to opt into. ## Scope - Parser for the subset of fields we care about: kind, metadata.name, spec.owner, spec.type, spec.system, spec.dependsOn. - Surface in the dashboard: owner badge, type filter, dependency edges between indexed repos. - Ignore unknown fields, do not validate the full Backstage schema. ## Out of scope - Authoring/scaffolding the file. - TechDocs, Scorecards, or any other Backstage surface (separate issues). - Bidirectional sync with a running Backstage instance. Cross-ref: discussion comparing repo-recall to Backstage, decided to cherry-pick features rather than ship a Backstage plugin.

coilysiren referenced this issue

2026-05-23 20:55:28 +00:00

Session timeline view: tool calls, tokens, subagent spawns over time #61

coilysiren commented

2026-05-30 05:43:55 +00:00

Author

Owner

Iceboxed in the 2026-05-29 backlog burn-down: Adopt Backstage catalog-info, far-future platform play. Reopen anytime if it becomes real.

coilysiren closed this issue

2026-05-30 05:43:55 +00:00

coilysiren added the

label