Skip to content

chore: remove .yarn/ci-cache from git and ignore it #22755

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

shivraj2805
Copy link

What does this PR do?

This PR removes Yarn CI cache files (install-state.gz) under packages/**/.yarn/ci-cache/ which were mistakenly committed and tracked in Git. These files are intended for CI caching only and do not belong in version control.

Removing them helps reduce repository size and keeps Git history clean. .gitignore is also updated to prevent future additions of these cache files.

Visual Demo (For contributors especially)

Image Demo:

Before After
.yarn/ci-cache/install-state.gz was tracked in Git .yarn/ci-cache/ is now ignored and removed from Git

No code functionality is affected — this change is purely for repository hygiene.

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox. → N/A
  • I confirm automated tests are in place that prove my fix is effective or that my feature works. → N/A

How should this be tested?

  • Confirm that .yarn/ci-cache/install-state.gz files are no longer tracked via git status.
  • Confirm .gitignore includes:
    packages/**/.yarn/ci-cache/

@shivraj2805 shivraj2805 requested a review from a team as a code owner July 26, 2025 09:56
Copy link

vercel bot commented Jul 26, 2025

@shivraj2805 is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

@graphite-app graphite-app bot added the community Created by Linear-GitHub Sync label Jul 26, 2025
@graphite-app graphite-app bot requested a review from a team July 26, 2025 09:56
@github-actions github-actions bot added ci area: CI, DX, pipeline, github actions 🐛 bug Something isn't working labels Jul 26, 2025
Copy link
Contributor

coderabbitai bot commented Jul 26, 2025

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (4)
  • packages/platform/constants/.yarn/ci-cache/install-state.gz is excluded by !**/.yarn/**, !**/*.gz
  • packages/platform/enums/.yarn/ci-cache/install-state.gz is excluded by !**/.yarn/**, !**/*.gz
  • packages/platform/types/.yarn/ci-cache/install-state.gz is excluded by !**/.yarn/**, !**/*.gz
  • packages/platform/utils/.yarn/ci-cache/install-state.gz is excluded by !**/.yarn/**, !**/*.gz

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A new rule has been added to the .gitignore file to ignore all .yarn/ci-cache/ directories located within any subdirectory of packages/. This update is appended to the end of the existing .gitignore file, and no other ignore rules are modified or removed. There are no changes to any code, configuration, or declarations of exported or public entities.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.gitignore (1)

100-103: Redundant ignore rule – already covered by earlier “.yarn/*” pattern

The rule on line 102 is functionally redundant because the existing pattern
.yarn/* (line 93) ignores every .yarn sub-directory at any depth.
Adding a second, narrower rule does no harm, but it increases noise in a file
that is already long and occasionally hard to scan.

If you prefer to keep the explicit reference for clarity, consider adding an
inline comment so future maintainers know it is intentional. Otherwise, the
simplest option is to delete the extra lines:

-
-
-packages/**/.yarn/ci-cache/
-
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ee073cd and d27eb4e.

⛔ Files ignored due to path filters (2)
  • packages/app-store-cli/.yarn/ci-cache/install-state.gz is excluded by !**/.yarn/**, !**/*.gz
  • packages/prisma/.yarn/ci-cache/install-state.gz is excluded by !**/.yarn/**, !**/*.gz
📒 Files selected for processing (1)
  • .gitignore (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Detect changes

Copy link

graphite-app bot commented Jul 26, 2025

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (07/26/25)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add community label" took an action on this PR • (07/26/25)

1 label was added to this PR based on Keith Williams's automation.

@shivraj2805 shivraj2805 requested review from a team as code owners July 27, 2025 02:34
Copy link
Contributor

@volnei volnei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, it's a good practice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working ci area: CI, DX, pipeline, github actions community Created by Linear-GitHub Sync
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove packages/**/.yarn/ci-cache/install-state.gz from git?
4 participants