Skip to content

Fix #894: Committed Build Artifacts in VCS - #975

Open
rudreshborle wants to merge 2 commits into
csxark:mainfrom
rudreshborle:feature/issue-894
Open

Fix #894: Committed Build Artifacts in VCS#975
rudreshborle wants to merge 2 commits into
csxark:mainfrom
rudreshborle:feature/issue-894

Conversation

@rudreshborle

Copy link
Copy Markdown
Contributor

Pull Request

Description

This PR addresses the issue of committed build artifacts in VCS by removing unnecessary files from Git tracking and updating the .gitignore file. The removed files include ESLint reports, TypeScript build output, and incremental build cache.


Related Issue

Fixes #894


Type of Change

  • Refactoring
  • Bug Fix

Changes Made

  1. Added patterns to .gitignore for *.tsbuildinfo, eslint-report*.json, tscconfig.txt, and issues-audit.txt.
  2. Removed files from Git tracking:
    • eslint-report2.json
    • tscconfig.txt
    • tsconfig.tsbuildinfo
    • issues-audit.txt

Testing

  • Static/syntax verification passed; automated tests were unavailable.

Screenshots

N/A


Checklist

  • My code follows the project guidelines.
  • I have tested my changes. (Note: Static/syntax verification passed; automated tests were unavailable.)
  • I have updated the documentation if required.
  • My changes address the related issue.
  • This PR focuses on a single issue.

Additional Notes

No additional notes are necessary at this time.

@vercel

vercel Bot commented Aug 10, 2026

Copy link
Copy Markdown

@rudreshborle is attempting to deploy a commit to the csxark's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions

Copy link
Copy Markdown
Contributor

🎉 Thank You for Your Contribution

Hello @rudreshborle,

Thank you for submitting a Pull Request to CryptoViz. We appreciate the time and effort you've invested in contributing to the project.

Your Pull Request has been received successfully and will be reviewed by the maintainers as soon as possible.

📋 Pull Request Checklist

  • ✅ Linked the related issue
  • ✅ No merge conflicts
  • ✅ Synced with the latest main branch
  • ✅ Build passes successfully
  • ✅ All tests pass

Ensuring these requirements are met helps streamline the review process and enables maintainers to review your contribution more efficiently.

❤️ Support CryptoViz

If you find CryptoViz helpful, consider supporting the project by:

  • ⭐ Starring the repository
  • 🍴 Forking the repository
  • 👤 Following Ark on GitHub
  • 💼 Connecting on LinkedIn
  • 🌐 Visiting the Portfolio

Your support helps increase the project's visibility and encourages continued development. Thank you for being a part of the CryptoViz community!

Thank you once again for contributing to CryptoViz. We appreciate your support and look forward to reviewing your contribution.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@rudreshborle, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dac61eeb-bf75-4772-9fdf-4ccca1c0dbcd

📥 Commits

Reviewing files that changed from the base of the PR and between 42227fa and 7140a21.

📒 Files selected for processing (3)
  • apps/cli/main.py
  • lib/offline/precacheRoutes.ts
  • public/sw.js

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@csxark csxark added ECSoC26 Elite Coders Summer of Code 2026 and removed needs review labels Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ECSoC26 Elite Coders Summer of Code 2026

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Committed Build Artifacts in VCS

2 participants