Describe recurring-events and its API in the repository catalog #54
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Personal/backstage#54
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Make the recurring-events service and its API self-describing in the owning Forgejo repository so Backstage can discover both from repository-owned metadata.
Context
The portal currently defines the recurring-events Component and recurring-events-api API in central example catalog files. The Personal/recurring-events repository contains openapi.yaml but does not currently have a root catalog-info.yaml.
Scope
Acceptance criteria
Related
martin referenced this issue2026-11-21 21:10:42 +00:00
Superseded: this repository-level task now lives with the code it changes at Personal/recurring-events#61. Continue there; this issue is being closed to avoid duplicate tracking.