Long-term, this dashboard could support more than just GitHub. Renaming the project (and config namespace) to something provider-neutral — e.g. git-dashboard — would leave room for GitLab, Bitbucket, and other Git-hosting providers down the line.
Scope to think about if/when we do this:
- Repo name and package names (
@github-dashboard/* → @git-dashboard/*)
- Config path:
~/.config/github-dashboard/config.yml → ~/.config/git-dashboard/config.yml (with a graceful migration)
- Binary/CLI name, Electron app id, display name
- Schema: the
instances shape would likely grow a provider: discriminator (github, gitlab, bitbucket)
- All docs and README
Long-term, this dashboard could support more than just GitHub. Renaming the project (and config namespace) to something provider-neutral — e.g.
git-dashboard— would leave room for GitLab, Bitbucket, and other Git-hosting providers down the line.Scope to think about if/when we do this:
@github-dashboard/*→@git-dashboard/*)~/.config/github-dashboard/config.yml→~/.config/git-dashboard/config.yml(with a graceful migration)instancesshape would likely grow aprovider:discriminator (github,gitlab,bitbucket)