What I Built
I built Nexus Observatory, a production-grade real-time visualization dashboard that pulls data from over 50,000 GitHub repositories stored in a Supabase PostgreSQL database to showcase worldwide developer activity. It features animated counters for total contributions (stars + commits), a dynamic pixelated world map with geographic distribution based on language-to-country proxy mapping, live sentiment analysis on commit messages using the VADER algorithm, an interactive "Peak Storm" mode that multiplies activity visuals, and a responsive UI with dark futuristic styling. For me, living in New Delhi where the tech scene is booming with open-source contributions from India, this project is a personal tribute to the global developer community—it's my way of making abstract GitHub data feel alive and engaging, highlighting how contributions from places like India connect to the world.
Demo
Check out the live deployment here: Nexus Observatory
For a quick walkthrough, here's a demo video showing the dashboard in action, including real-time updates, map interactions, and storm mode activation:
Screenshots:
Nexus Observatory dashboard overview with animated contribution counters, stats grid, and top countries leaderboard
Pixelated world map visualization in peak storm mode with colored intensity dots representing global developer activity
My Experience with GitHub Copilot CLI
Throughout building Nexus Observatory, GitHub Copilot CLI was my go-to for accelerating terminal-based tasks, especially in a project heavy on database integration and API routes. For example, when setting up the Supabase connection and writing initial migration scripts, I used gh copilot suggest to generate shell commands like "Create a Supabase client with anon key and run a query to fetch total repos," which outputted precise code snippets I could pipe directly into my scripts—saving me from manual trial-and-error. It was invaluable for git workflows too; suggesting commit messages such as "feat: integrate language-to-country proxy mapping in countries/stats API" after major refactors, or even helping craft a deployment script for Vercel with error checks and env variable handling. Overall, it cut my development time by about 40%, making the shift from synthetic data to real Supabase queries feel seamless and collaborative, even as a solo dev. The CLI's suggestions were spot-on for debugging SQL queries right in the terminal without switching contexts.
Top comments (0)