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
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.pyhas anormalize_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
normalize_repo_args().{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