❌ Console Statements Detected

Found 1 file(s) with console statements that should be removed.

Why remove console statements?

• The project has sufficient error tracking in place
• Console statements can expose sensitive information in production
• They can clutter browser console logs
• They may impact performance in production builds

Files with violations:

website/static/js/repo_detail.js:

29:        console.error('Failed to copy text: ', err);
100:            console.error('CSRF token not found. Make sure cookies are enabled or the CSRF meta tag exists.');
129:            console.error('Error parsing response:', parseError);
312:        console.error('Error:', error);
379:            console.error('Error:', error);
443:        console.error('Error fetching stargazers:', error);

How to fix:

1. Remove or comment out all console.* statements from your code (console.log, console.error, console.warn, etc.)
2. Use the project's existing error tracking system for debugging
3. For temporary debugging during development, comment out console statements: // console.log()

Note:

• All console methods (log, error, warn, debug, info, etc.) are forbidden.
• If console statements are inside a multi-line comment block (/* ... */), they may still be flagged. Please manually verify.

Please remove all console statements and push your changes.