Automatically change the current working directory to the new worktree

[lambdalisue]

Summary by CodeRabbit

• New Features
  • Automatically switches the working directory to the new worktree location after creating a worktree.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The update modifies the doNew and doNewOrphan functions in the worktree management module to automatically change the current working directory to the path of the newly created worktree immediately after its creation.

Changes

File(s)	Change Summary
denops/gin/action/worktree_new.ts	Updated doNew and doNewOrphan to change directory to new worktree after creation.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant doNew/doNewOrphan
    participant WorktreeAdd
    participant ChangeDir

    User->>doNew/doNewOrphan: Initiate worktree creation
    doNew/doNewOrphan->>WorktreeAdd: Add new worktree
    WorktreeAdd-->>doNew/doNewOrphan: Return worktree path
    doNew/doNewOrphan->>ChangeDir: Change directory to new worktree path
    ChangeDir-->>doNew/doNewOrphan: Directory changed
    doNew/doNewOrphan-->>User: Operation complete

Loading

Possibly related PRs

• lambdalisue/vim-gin#159: Modifies doNew and doNewOrphan to determine the Git root directory for the worktree path, affecting the same functions and related logic for worktree path handling.

Poem

A hop and a skip, a new worktree appears,
Now the rabbit jumps where the new path steers.
With a wiggle of code and a change so spry,
The working directory follows, oh my!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7ef9dfa and 22c6ee7.

📒 Files selected for processing (1)

• denops/gin/action/worktree_new.ts (2 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.30%. Comparing base (7ef9dfa) to head (22c6ee7).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #160   +/-   ##
=======================================
  Coverage   60.30%   60.30%           
=======================================
  Files          17       17           
  Lines         912      912           
  Branches      120      120           
=======================================
  Hits          550      550           
  Misses        362      362           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.