Skip to content

ARCH-33: Transfer front-end-guild ownership to reporting-backend - #138

Draft
dep wants to merge 1 commit into
masterfrom
agent/arch-33-transfer-ownership-1d1f
Draft

ARCH-33: Transfer front-end-guild ownership to reporting-backend#138
dep wants to merge 1 commit into
masterfrom
agent/arch-33-transfer-ownership-1d1f

Conversation

@dep

@depdep commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

https://invoca.atlassian.net/browse/ARCH-33

Transfer live ownership of backdraft from @Invoca/front-end-guild to @Invoca/reporting-backend (Omega), per ARCH-33.

Changes

  • catalog-info.yaml: spec.owner: front-end-guildreporting-backend

Repo search found no other live front-end-guild / frontend-guild / @Invoca/front-end-guild ownership hits. Historical deprecation prose in the catalog description does not name the guild as the current owner, so it was left unchanged. This repo has no CODEOWNERS file.

pr_agent:summary

Open in WebOpen in Cursor

Move Backstage spec.owner from front-end-guild to reporting-backend
(Omega) so catalog routing matches the ARCH-33 ownership decision.
Co-authored-by: Danny Peck <dannypeck@gmail.com>

@unblockedunblockedBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No issues found

About Unblocked

Unblocked has been set up to automatically review your team's pull requests to identify genuine bugs and issues.

📖 Documentation — Learn more in our docs.

💬 Ask questions — Mention @unblocked to request a review or summary, or ask follow-up questions.

👍 Give feedback — React to comments with 👍 or 👎 to help us improve.

⚙️ Customize — Adjust settings in your preferences.

Sign up for freeto 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.

2 participants

@dep@cursoragent