YK
Move the API endpoints section into a separate file and add more details about how to get started with Kaguya - install it as a ChatGPT plugin and move all...
Current UI:  "up to 100" is a bit awkward there. Maybe we can add something in the repo filtering view instead. If there are 100 repos shown there, we...
@joshenlim's note: > I realised pulling issue tracking on demand (skipping lambda) might be possible: ``` { repository(owner: "supabase", name: "supabase") { issues(first: 100) { totalCount edges { node {...
When the user selects repos, the UI doesn't make it too clear which repos have been selected:  I think it should show it like, "selected repos: supabase, supabase-js, realtime,...
On the new layout, we're showing the URL twice - and I'm thinking it might not be necessary:  I'm not sure what would be a good solution for it...
This is so that when the app exceeds the API limit for the other orgs, users will at least be able to check Supabase's page as an example.
When showing a star history for a whole org, it should work even when the org has 100+ repos
Even though we added a timeZone support here (https://github.com/propeldata/ui-kit/pull/110), we don't have documentation on this feature yet. We should make sure that it's documented for Counter, TimeSeries and Leaderboard. For...