While building GitScope, I ran into two bugs that caused major issues during testing.
GitScope is an open-source GitHub profile analyzer that turns GitHub data into developer insights, scores, and recommendations.
Bug #1: Custom Domain Deployment Failure
After deploying GitScope, my custom domain would not connect correctly.
The issue was in my netlify.toml configuration. I had not configured the publish directory properly, so Netlify was not pointing to the correct build output.
After fixing the configuration to use the correct dist directory and redeploying, the domain worked.
Bug #2: Developer Scores Not Showing
The second issue was with the frontend state.
GitHub profile data was loading, but the generated developer scores were not appearing in the UI.
I traced the flow:
GitHub Data → Analysis → Score Generation → Frontend State → UI
The issue was in how the frontend handled the returned analysis data. After fixing the state handling, scores displayed correctly.
What I Learned
These bugs showed me that small configuration and state issues can completely break an application.
Debugging GitScope helped me better understand how deployment, data processing, and frontend systems connect together.
Top comments (0)