Application is missing a lot of Repositories
bsunderhus opened this issue · comments
Right now the application is using the repository naming convention to find out which department (Frontend, Backend, Android or IOS) the repository belongs to. This has been proved to be inefficient as most of the repositories are not actually following this convention.
To ensure a better repository match @dannytce suggested using the Github Topics
The idea would be to basically add a meaningful topic to the repository describing its department and then consuming this information through the Github GraphQL API
I like this idea. It has some upsides that came into mind:
-
Configurability: Ideally, in a later future, one should be able to configure what topics to use for this kind of separation, meaning if we open the project to other uses it will be quite covered. We can still maintain a tab with All projects as default, making this functionality optional.
-
Flexibility: If there's a mono-repo, we can still tag it with more than one topic to ensure it appears on all related tabs.