Skip to content

feat: merge branches#110

Open
LemonNekoGH wants to merge 1 commit into
mainfrom
lemonnekogh/user-branch-merging-eb49
Open

feat: merge branches#110
LemonNekoGH wants to merge 1 commit into
mainfrom
lemonnekogh/user-branch-merging-eb49

Conversation

@LemonNekoGH
Copy link
Copy Markdown
Owner

No description provided.

Co-authored-by: self <self@lemonneko.moe>
@LemonNekoGH LemonNekoGH self-assigned this Jan 21, 2026
@LemonNekoGH LemonNekoGH added the help wanted Extra attention is needed label Jan 21, 2026
@netlify
Copy link
Copy Markdown

netlify Bot commented Jan 21, 2026

Deploy Preview for flow-chat ready!

Name Link
🔨 Latest commit 1f6489c
🔍 Latest deploy log https://app.netlify.com/projects/flow-chat/deploys/697094c8c03b120008491025
😎 Deploy Preview https://deploy-preview-110--flow-chat.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @LemonNekoGH, 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 introduces a significant new feature that enables users to merge conversation branches. It provides a user-friendly interface through context menus and toolbars, along with a dedicated dialog for selecting the branch to merge. The underlying logic ensures that messages are correctly integrated into the target conversation path, enhancing the flexibility of conversation management.

Highlights

  • New 'Merge' Functionality: Introduced the ability to merge different branches of a conversation, allowing users to combine message histories.
  • UI Integration: Added 'Merge' options to both the conversation node context menu and the node toolbar for easy access.
  • Merge Logic Implementation: A new mergeBranch action was added to the message store, which intelligently appends unique messages from a selected source branch to a target branch.
  • Interactive Merge Dialog: A dedicated dialog has been implemented to guide users through the merge process, allowing them to select a specific branch to merge from a list of candidates.

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

Copy link
Copy Markdown

@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 introduces a new 'merge branches' feature, allowing users to combine conversation branches. The changes include adding 'merge' events and UI elements across ConversationNodeContextMenu.vue, ConversationView.vue, and NodeToolbar.vue. The core logic for identifying merge candidates and performing the merge operation is implemented in src/pages/chat/[id].vue and src/stores/messages.ts. The implementation appears robust, handling common ancestors and appending messages correctly. The UI for selecting branches is clear and user-friendly.

Comment thread src/stores/messages.ts
currentParentId,
msg.provider,
msg.model,
msg.room_id!,
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The room_id property of msg is asserted as non-null using !. While messages retrieved from getByRoomId are expected to have a non-null room_id, the Message type itself allows room_id: string | null. To improve type safety and prevent potential runtime errors if a message with a null room_id somehow makes it into sourcePath, it would be safer to explicitly handle the null case or ensure the type definition for messages in sourcePath guarantees a non-null room_id.

Suggested change
msg.room_id!,
msg.room_id as string,

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

Labels

help wanted Extra attention is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants