Support aliases repositories & default org in .gh repo command

[jb3]

Description

There are some repositories that we frequently want to reference with the .gh repo command, e.g. discord.py, Kubernetes, most PyDis repos.

We should support the following behaviour when the .gh repo command:

flowchart TD
    Start([User Input]) --> CheckFull{Full repo provided?<br/>user/reponame}
    
    CheckFull -->|Yes| UseFull[Use provided repo]
    CheckFull -->|No| CheckStored{Stored repo name?<br/>e.g. kubernetes}
    
    CheckStored -->|Yes| UseStored[Use stored mapping<br/>e.g. kubernetes/kubernetes]
    CheckStored -->|No| CheckPyDiscord{python-discord<br/>has this repo?<br/>e.g. site}
    
    CheckPyDiscord -->|Yes| UsePyDiscord[Use python-discord/reponame<br/>e.g. python-discord/site]
    CheckPyDiscord -->|No| Fail[Fail: Full user/repo<br/>must be provided]
    
    UseFull --> Success([Success])
    UseStored --> Success
    UsePyDiscord --> Success
    Fail --> End([End])
    Success --> End
    
    style Start fill:#e1f5ff,stroke:#0288d1,stroke-width:2px,color:#000
    style CheckFull fill:#fff9c4,stroke:#f57c00,stroke-width:2px,color:#000
    style CheckStored fill:#fff9c4,stroke:#f57c00,stroke-width:2px,color:#000
    style CheckPyDiscord fill:#fff9c4,stroke:#f57c00,stroke-width:2px,color:#000
    style UseFull fill:#c8e6c9,stroke:#388e3c,stroke-width:2px,color:#000
    style UseStored fill:#c8e6c9,stroke:#388e3c,stroke-width:2px,color:#000
    style UsePyDiscord fill:#c8e6c9,stroke:#388e3c,stroke-width:2px,color:#000
    style Success fill:#a5d6a7,stroke:#2e7d32,stroke-width:3px,color:#000
    style Fail fill:#ffcdd2,stroke:#c62828,stroke-width:2px,color:#000
    style End fill:#e1f5ff,stroke:#0288d1,stroke-width:2px,color:#000

Loading

As a set of initial repositories:

• Popular libraries we get questions about: e.g. discord.py -> Rapptz/discord.py
• Have a look at some of the other DevOps tooling for other repos to maybe include (kubernetes, ansible)
• Additionally large projects within Python ecosystem (e.g. numpy, uv, poetry)

We should probably store this in an external resource file rather than embedded into the implementation

One thing I will stipulate is: our aliased version must be the same repo name (e.g. Rapptz/discord.py must be discord.py, not discord, kubernetes must be kubernetes not k8s, etc.)

Would you like to implement this yourself?

• I'd like to implement this feature myself
• Anyone can implement this feature

[onerandomusername]

Here's an implementation that simply matches to the highest starred repo with that name on GitHub, which would seemingly be easier than a resource file.

https://github.com/ghostty-org/discord-bot/blob/a4e99109acfc206f128f5909cc3c03bc03335dcf/app/components/github_integration/entities/resolution.py#L48-L56

[jb3]

Updating after discussion on Discord:

We will still use a resource file that defines mappings of repos to a fully expanded version (e.g. kubernetes -> kubernetes/kubernetes), but we will replace the failed stage with the search mentioned above.

Updated flow chart follows, we are basically removing our failure state.

flowchart TD
    Start([User Input]) --> CheckFull{Full repo provided?<br/>user/reponame}
    
    CheckFull -->|Yes| UseFull[Use provided repo]
    CheckFull -->|No| CheckStored{Stored repo name?<br/>e.g. kubernetes}
    
    CheckStored -->|Yes| UseStored[Use stored mapping<br/>e.g. kubernetes/kubernetes]
    CheckStored -->|No| CheckPyDiscord{python-discord<br/>has this repo?<br/>e.g. site}
    
    CheckPyDiscord -->|Yes| UsePyDiscord[Use python-discord/reponame<br/>e.g. python-discord/site]
    CheckPyDiscord -->|No| SearchGitHub[Search GitHub for<br/>matching repos<br/>sorted by stars]
    
    UseFull --> Success([Success])
    UseStored --> Success
    UsePyDiscord --> Success
    SearchGitHub --> Success
    Success --> End([End])
    
    style Start fill:#e1f5ff,stroke:#0288d1,stroke-width:2px,color:#000
    style CheckFull fill:#fff9c4,stroke:#f57c00,stroke-width:2px,color:#000
    style CheckStored fill:#fff9c4,stroke:#f57c00,stroke-width:2px,color:#000
    style CheckPyDiscord fill:#fff9c4,stroke:#f57c00,stroke-width:2px,color:#000
    style UseFull fill:#c8e6c9,stroke:#388e3c,stroke-width:2px,color:#000
    style UseStored fill:#c8e6c9,stroke:#388e3c,stroke-width:2px,color:#000
    style UsePyDiscord fill:#c8e6c9,stroke:#388e3c,stroke-width:2px,color:#000
    style SearchGitHub fill:#c8e6c9,stroke:#388e3c,stroke-width:2px,color:#000
    style Success fill:#a5d6a7,stroke:#2e7d32,stroke-width:3px,color:#000
    style End fill:#e1f5ff,stroke:#0288d1,stroke-width:2px,color:#000

Loading

[mhaxanali]

I'm more than willing to implement this. I recently contributed the quote commands (#1707) and would love to work on improving the .gh repo command with alias support and default org functionality.

[mhaxanali]

Also it could be possible that no such repository exists, in that case we do have a failure.