Repository navigation
Feat: multi-owner repos in report.py (carry owner through data model) #37
Description
Companion to the RepoMan epic rossoctl/automation#72. Implemented as part of Phase 1 (rossoctl/automation#78); do not start until that phase begins.
Problem
github-weekly-report/scripts/report.py has a normalize_repo_args() step that rejects cross-owner repo arguments and strips the owner, assuming a single global org. RepoMan's per-repo {owner, name} model needs the owner carried through end to end.
Scope
- Remove the cross-owner rejection in
normalize_repo_args(). - Carry
{owner, name}as a pair through the report data model instead of stripping owner, so a report can span repos from multiple owners.
Sequencing
Blocked by Phase 1 (rossoctl/automation#78): the {owner, name} input model in the automation scripts is what feeds this. Ships alongside or just after that phase.
Assisted-By: Claude Code
Activity
feat: Support multi-owner repo sets in weekly report
rubambiza commentedon Oct 13, 2026
Closing as implemented. Owner is carried through the data model in
skills/github-weekly-report/scripts/report.py:get_reposreturns{owner,name}dicts,normalize_repo_argsparsesowner/repoand rejects ambiguous bare names, each repo is fetched against its own owner, and a multi-owner header renders. Landed in81b87d1(feat: Support multi-owner repo sets in weekly report).