Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Start workspace without asking when pressing the play button

未关闭
#331 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
typescript
领域
developer-experience, devtools

调研方向

跟踪 play-button、dashboard 和 recents 入口点，以及远程 SSH 插件激活钩子。首先确定该钩子是否能够区分初始连接和重新连接。完成的标准是：通过 play-button 和 dashboard 启动时，工作区无需提示即可启动，而重新连接不会自动启动已自动停止的工作区。

由索引模型根据 Issue 内容生成。

描述

Currently, the play button immediately calls out to the remote SSH plugin.

Then, our plugin hooks into the remote SSH plugin activation and it does its magic like starting the workspace.

Problem is, we cannot tell if the remote SSH plugin was activated due to the play button being pressed or due to a reconnect. We cannot auto-start on reconnects because it causes issues with auto-stopped workspaces (VS Code will keep reconnecting and keep turning workspaces on, preventing the cost savings).

So, assuming there is no clever way to tell what caused the connect, I think we will just have to duplicate the start code when you press that button. Then delegate to the remote SSH plugin.

Another case where you probably want the workspace to start without asking is from the recents menu, but that goes straight to the remote SSH plugin so I am not sure there is anything we can do there. Is there some way in the remote authority activation hook to tell what caused the connect? If we can distinguish between a first connect and a reconnect, that would be ideal.

Another case is when coming in from the dashboard. This could be handled like the play button by duplicating the start code.

主要语言
TypeScript
星标
131
派生
48
平均合并
4 天 21 小时
30 天内合并 PR
14

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

coder/vscode-coder 的其他 Issue

查看 coder/vscode-coder 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。