fix: follow up prompts

[Shironex]

Changes from branch fix/followup-run

• closes [Bug]: After committing a change from a work-tree, refinement changes appear in main repo, not worktree previously used #457

Summary by CodeRabbit

• Refactor
  • Updated follow-up feature API parameters to use boolean flags instead of string paths for improved consistency across internal modules.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR refactors the follow-up feature API to use a boolean flag indicating whether to use worktrees instead of passing a worktree path string. The parameter change is propagated through the UI hook, Electron API interface, and HTTP client layers.

Changes

Cohort / File(s)	Summary
UI Hook Integration apps/ui/src/components/views/board-view/hooks/use-board-actions.ts	Added useWorktrees as a new public prop to UseBoardActionsProps interface; destructured and propagated through hook parameters, dependency arrays, and handleSendFollowUp API call
API Interface Updates apps/ui/src/lib/electron.ts, apps/ui/src/lib/http-api-client.ts	Renamed followUpFeature method parameter from worktreePath?: string to useWorktrees?: boolean in both Electron API interface and HTTP client implementation; updated request payload to use useWorktrees instead of worktreePath

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat: enhance UI components and branch management #161: Directly modifies the followUpFeature API surface by replacing worktreePath with useWorktrees flag across multiple layers
• worktree-select #182: Updates use-board-actions.ts to add and propagate worktree-related props and handlers for feature/worktree creation

Poem

🐰 A worktree's path now simplifies,
To just a flag before our eyes—
Through hooks and clients, changes flow,
Parameter dance, a cleaner glow! 🌿

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'fix: follow up prompts' is vague and doesn't clearly convey the specific change made in this PR, which is refactoring parameters from worktreePath to useWorktrees flag.	Consider a more specific title that reflects the actual change, such as 'refactor: Replace worktreePath param with useWorktrees flag in follow-up prompts' to better communicate the nature of the modification.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Shironex, I'm Gemini Code Assist¹! 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 refactors the followUpFeature functionality by modifying its API signature and implementation. The explicit worktreePath parameter has been replaced with a useWorktrees boolean flag, streamlining how worktree usage is communicated for follow-up prompts. This change impacts the UI component, the Electron API interface, and the HTTP API client, ensuring consistent handling of worktree-related logic.

Highlights

• API Signature Update: The followUpFeature API method has been updated across the UI, Electron API, and HTTP client to replace the worktreePath string parameter with a useWorktrees boolean flag.
• Simplified Worktree Handling: This change abstracts the specific worktree path determination, allowing the system to handle it internally based on a simple boolean flag, leading to a cleaner API interface.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

[gemini-code-assist]

Code Review

This pull request refactors the followUpFeature API to accept a useWorktrees boolean flag instead of a worktreePath string. The changes are consistently applied across the UI, API definitions, and mock implementations, which is great.

I've added one suggestion to further improve the maintainability of the followUpFeature function by consolidating its parameters into a single options object. This will make the function signature cleaner and more extensible.

[Shironex]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.