• top languages of the user
• limit the number of displayed languages
• filter out specific languages

Currently, we are using hard-coded graphql query strings for API calls.
Find a way to manage them via .gql files but ensure no performance drops.

• husky
• lint-staged
• prettier

Move and manage the cases and handlers on separate files. This issue is specified to the express app only.

Basic

• number of discussions opened by the user
• number of answered discussions
• number of user's comments on the discussions

Optional

• list of all repositories with the main image by order
• list of the repositories with answered discussions

• basic profile
• discussions
• open source contributions
• top languages

Extends #2

The tests need to be clear and make sure all features are not failing.

• discussions
• contributions
• languages

Like languages and discussions, contribution needs to be refactored as well.

GitHub Actions and Vercel for now

• list of repo order by most contribution and their avatar image
• filter by stars on the repo
• filter out by repo | owner | owner/repo names
• filter by owner account type (all, user, org) - default org
• choose whether to display as owner/repo

• #30
• #3
• #21
• #14

If using octokit is way simpler than querying by fetch and not much difference in performance, then implement it.