Skip to content

Revert "Revert "feat!: specify claude dir with CLAUDE_CONFIG_DIR and remove -p/--path option""#77

Merged
ryoppippi merged 1 commit intomainfrom
revert-76-revert-70-copilot/fix-4a5d6a32-927f-4cf5-be0f-269b8b06a70d
Jun 16, 2025
Merged

Revert "Revert "feat!: specify claude dir with CLAUDE_CONFIG_DIR and remove -p/--path option""#77
ryoppippi merged 1 commit intomainfrom
revert-76-revert-70-copilot/fix-4a5d6a32-927f-4cf5-be0f-269b8b06a70d

Conversation

@ryoppippi
Copy link
Owner

Reverts #76

@coderabbitai
Copy link

coderabbitai bot commented Jun 16, 2025

Warning

Rate limit exceeded

@ryoppippi has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 36 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 3d51ecc and 3bd4022.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (10)
  • .github/workflows/ci.yaml (1 hunks)
  • README.md (4 hunks)
  • package.json (1 hunks)
  • src/commands/daily.ts (3 hunks)
  • src/commands/mcp.ts (2 hunks)
  • src/commands/monthly.ts (3 hunks)
  • src/commands/session.ts (3 hunks)
  • src/data-loader.test.ts (2 hunks)
  • src/data-loader.ts (1 hunks)
  • src/shared-args.internal.ts (0 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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 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.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedpath-type@​6.0.01001008577100

View full report

@ryoppippi ryoppippi merged this pull request into main Jun 16, 2025
10 checks passed
@ryoppippi ryoppippi deleted the revert-76-revert-70-copilot/fix-4a5d6a32-927f-4cf5-be0f-269b8b06a70d branch June 16, 2025 16:17
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @ryoppippi, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request re-implements the strategy for specifying the Claude data directory, shifting from a command-line option (--path) to an environment variable (CLAUDE_CONFIG_DIR). This change centralizes the configuration of the data directory, ensuring all commands consistently locate Claude data based on the environment variable, and includes robust validation and updated documentation.

Highlights

  • Configuration Method Change: The --path command-line option for specifying the Claude data directory has been removed. The tool now exclusively uses the CLAUDE_CONFIG_DIR environment variable for this purpose.
  • Core Logic Adaptation: All commands (daily, monthly, session, mcp) have been updated to retrieve the Claude data directory path via a new getDefaultClaudePath() utility function, which prioritizes the CLAUDE_CONFIG_DIR environment variable.
  • Documentation Update: The README.md has been thoroughly updated to reflect the new configuration method, including revised command examples and a dedicated section explaining the use of the CLAUDE_CONFIG_DIR environment variable.
  • Path Validation and Testing: The getDefaultClaudePath() function now includes robust validation to ensure the specified Claude data directory exists and is a valid directory. Comprehensive unit tests have been added to cover various scenarios for this function, including environment variable presence, default path fallback, and error handling for invalid paths.
  • New Dependency: A new dependency, path-type, has been introduced to facilitate reliable checks for directory existence.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jun 16, 2025

Open in StackBlitz

npm i https://pkg.pr.new/ryoppippi/ccusage@77

commit: 3bd4022

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request reverts the previous feature that allowed specifying the Claude directory with the -p or --path option, and instead relies solely on the CLAUDE_CONFIG_DIR environment variable. The changes primarily involve removing the --path argument and updating the code to use getDefaultClaudePath() to determine the Claude data directory. The README has also been updated to reflect these changes.

Comment on lines +25 to +30
if (!isDirectorySync(envClaudeCodePath)) {
throw new Error(
` Claude data directory does not exist: ${envClaudeCodePath}.
Please set CLAUDE_CONFIG_DIR to a valid path, or ensure ${DEFAULT_CLAUDE_CODE_PATH} exists.
`.trim(),
);
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The error message could be improved by suggesting the user create the default directory if they intend to use it. Also, consider adding a newline after the directory name in the error message for better readability.

		throw new Error(
			`Claude data directory does not exist: ${envClaudeCodePath}.\n` +
			`Please set CLAUDE_CONFIG_DIR to a valid path, or ensure ${DEFAULT_CLAUDE_CODE_PATH} exists (you may need to create it).`
		);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant