Summary
The build/ directory is visible in the repository file tree. This is the compiled Webpack output intended for deployment, not source code. Committing build artifacts is a serious repository hygiene problem: it inflates repo size, causes merge conflicts on every build, and means contributors might accidentally use stale compiled output instead of building from source.
Problem
build/ is tracked in Git despite containing compiled JavaScript bundles, minified CSS, and binary assets.
Every npm run build by any contributor will produce a different build/ output (different hash names), causing unnecessary diff noise and merge conflicts.
Netlify (the deployment platform per the README) builds from source automatically — committing build/ serves no functional purpose.
Proposed Solution
Add build/ to .gitignore immediately.
Remove build/ from the repository history using git rm -r --cached build/.
Verify that Netlify's build configuration (npm run build) is correctly set in the Netlify dashboard so deployment is not affected.
I will also check for any other compiled artifacts (e.g., dist/, *.map files in unexpected locations) and clean those up in the same PR.
Labels: bug, repository hygiene, critical, GSSoC 2026
Summary
The build/ directory is visible in the repository file tree. This is the compiled Webpack output intended for deployment, not source code. Committing build artifacts is a serious repository hygiene problem: it inflates repo size, causes merge conflicts on every build, and means contributors might accidentally use stale compiled output instead of building from source.
Problem
build/ is tracked in Git despite containing compiled JavaScript bundles, minified CSS, and binary assets.
Every npm run build by any contributor will produce a different build/ output (different hash names), causing unnecessary diff noise and merge conflicts.
Netlify (the deployment platform per the README) builds from source automatically — committing build/ serves no functional purpose.
Proposed Solution
Add build/ to .gitignore immediately.
Remove build/ from the repository history using git rm -r --cached build/.
Verify that Netlify's build configuration (npm run build) is correctly set in the Netlify dashboard so deployment is not affected.
I will also check for any other compiled artifacts (e.g., dist/, *.map files in unexpected locations) and clean those up in the same PR.
Labels: bug, repository hygiene, critical, GSSoC 2026