chore: hand ownership to product-actions - #233
Merged
Merged
Conversation
Three sources disagreed about who owns this repo, and the disagreement was invisible because none of them contradicted each other loudly: .github/CODEOWNERS @Staffbase/cc-tech catalog-info.yaml no spec.owner at all Backstage cc-tech, inferred from CODEOWNERS infrastructure github/staffbase/repositories/teams/product-actions/ The Terraform home is the one that matches reality: this is the Node.js plugin skeleton generator, which belongs with Actions alongside the rest of the plugin tooling. CC Tech is not maintaining it. CODEOWNERS now names product-actions, and catalog-info.yaml declares the owner explicitly rather than leaving Backstage to infer one. Adding the github.com/team-slug annotation while here, so the catalog entry states its team rather than deriving it. Found by a repo-inventory reconciliation in customer-care-catalog: this repo showed up as cc-tech-owned in Backstage but was absent from the CC Tech inventory, because that inventory seeds from the infrastructure teams/cc-tech directory. Either the ownership or the directory was wrong; this resolves it in the direction the code actually points. No code, config or build change.
maximizeIT
requested review from
a team,
axdotl,
jyuliya,
maikirmscher and
taymoor0309
and removed request for
a team
August 10, 2026 15:17
maximizeIT
enabled auto-merge
August 10, 2026 15:21
staffbaseandres
approved these changes
Aug 10, 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
2 participants
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.
What
Hands ownership of this repo from CC Tech to @Staffbase/product-actions.
.github/CODEOWNERS: root*owner becomes@Staffbase/product-actions.catalog-info.yaml: declaresspec.owner: group:default/product-actionsexplicitly, and adds thegithub.com/team-slugannotation.No code, config or build change.
Why
Four sources disagreed about who owns this repo, quietly:
.github/CODEOWNERS@Staffbase/cc-techcatalog-info.yamlspec.ownerat allinfrastructuregithub/staffbase/repositories/teams/product-actions/create-staffbase-plugin-nodejs.ymlThe Terraform home matches reality: this is the Node.js plugin skeleton generator, which sits with Actions alongside the rest of the plugin tooling. CC Tech is not maintaining it, so the CODEOWNERS entry was the stale one.
Leaving
spec.ownerunset is what let the disagreement persist, since Backstage silently falls back to CODEOWNERS. It is now stated rather than inferred.How this surfaced
A repo-inventory reconciliation in customer-care-catalog: this repo appeared as cc-tech-owned in Backstage but was absent from the CC Tech inventory, which seeds from the
infrastructureteams/cc-tech/directory. Either the ownership or the directory was wrong. This resolves it in the direction the code actually points.For reviewers
@Staffbase/product-actions, this is the handover: after merge the repo is yours in CODEOWNERS and Backstage, matching where it already lives in
infrastructure. Shout if you consider it CC Tech's after all and we will move the Terraform file instead.The PR needs a CC Tech approval, since @Staffbase/cc-tech is still the current code owner of the file being changed.