Per Repo `gh` Authorisation Settings

[yaroslavyaroslav]

I have a separate scopes of mine pet projects and mine work projects. So I set up local authorisations per repo for gh + direnv to set up separate creds for separate repos. To make it PR review/create pipeline frictionless.

I would love to have the same approach in supacode to present ci/cd stats for each repo. Meaning the ability for supacode to read from a custom GH_CONFIG_DIR path for the creds to use them to retrieve CI/CD data from the repo.

So I'm raising this issue more for a discussion purpose, on these questions in specific:

1. If to implement one then general settings Github tab should be introduced in per repo basis. Any ideas what to present in general settings then? Some aggregation for complex cases and a single creds instance (as it is now) for a usual one?
2. Is there any blockers on ongoing tasks that would be better to be resolved before to start implementing this one? Like ongoing refactoring of a pref pane whatsoever?
3. Do you even consider this feature to be useful and thus to be merged on being implemented?

[sbertix]

Hey 👋 could definitely be useful, imho. Perhaps even more if paired with a more flashed out global and per-repo env support in general. What do you think?