Skip to content

feat(stage-*): allow to connect remote ws server#953

Merged
nekomeowww merged 4 commits intomainfrom
lemonnekogh/allow-to-connect-remote-ws
Jan 14, 2026
Merged

feat(stage-*): allow to connect remote ws server#953
nekomeowww merged 4 commits intomainfrom
lemonnekogh/allow-to-connect-remote-ws

Conversation

@LemonNekoGH
Copy link
Member

No description provided.

@LemonNekoGH LemonNekoGH self-assigned this Jan 14, 2026
@gemini-code-assist
Copy link
Contributor

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 enhancement by enabling the application to connect to external WebSocket servers. It provides users with a new settings interface to specify the WebSocket server address, which is then dynamically used by the underlying communication layer. This change improves the application's adaptability to different deployment environments and network setups, ensuring that the connection is automatically managed upon configuration updates.

Highlights

  • Remote WebSocket Server Connection: The application now supports connecting to a remote WebSocket server, allowing for more flexible network configurations.
  • New Connection Settings Page: A dedicated 'Connection' settings page has been added, enabling users to configure the WebSocket server URL.
  • Dynamic WebSocket URL Configuration: The WebSocket client has been updated to use a configurable URL, which is persisted in local storage.
  • Automatic Reconnection on URL Change: The WebSocket connection will automatically dispose and re-initialize when the configured WebSocket URL is changed.
Ignored Files
  • Ignored by pattern: packages/i18n/src/** (8)
    • packages/i18n/src/locales/en/settings.yaml
    • packages/i18n/src/locales/es/settings.yaml
    • packages/i18n/src/locales/ja/settings.yaml
    • packages/i18n/src/locales/ko/settings.yaml
    • packages/i18n/src/locales/ru/settings.yaml
    • packages/i18n/src/locales/vi/settings.yaml
    • packages/i18n/src/locales/zh-Hans/settings.yaml
    • packages/i18n/src/locales/zh-Hant/settings.yaml
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.

@LemonNekoGH LemonNekoGH force-pushed the lemonnekogh/allow-to-connect-remote-ws branch from 449ab82 to 5321410 Compare January 14, 2026 16:41
@github-actions
Copy link
Contributor

github-actions bot commented Jan 14, 2026

⏳ Approval required for deploying to Cloudflare Workers (Preview) for stage-web.

Name Link
🔭 Waiting for approval For maintainers, approve here

Hey, @nekomeowww, @sumimakito, @luoling8192, @LemonNekoGH, kindly take some time to review and approve this deployment when you are available. Thank you! 🙏

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 successfully implements a new feature allowing users to configure a remote WebSocket server URL. The changes are well-structured, introducing a new settings page in stage-pages and updating the channel-server store in stage-ui to use and react to the configured URL. The implementation correctly handles reconnecting when the URL is changed.

Copy link
Member

Choose a reason for hiding this comment

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

Let's not to translate for other languages, this should be done by another CI.

@nekomeowww nekomeowww merged commit 06b3451 into main Jan 14, 2026
4 of 9 checks passed
@nekomeowww nekomeowww deleted the lemonnekogh/allow-to-connect-remote-ws branch January 14, 2026 21:14
Joker-of-Gotham pushed a commit to Joker-of-Gotham/airi that referenced this pull request Jan 29, 2026
Joker-of-Gotham pushed a commit to Joker-of-Gotham/airi that referenced this pull request Jan 29, 2026
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.

2 participants