Migrate a NUKE build to Fallout from the command palette

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

@ChrisonSimtian 已经在做这个了。

开始于 2026年11月15日。

  • #36 来自 @ChrisonSimtian —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
58/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
csharp, vscode

调研方向

Start from package.json: the command has to be declared under contributes.commands before the palette can show it, and the existing tree-view registration is where the post-migration refresh hooks in. Detection of .nuke/ or Nuke.* and the remembered one-time prompt belong in workspace state; the run goes through vscode.window.createTerminal at the detected repo root, dry-run first, then the confirmed run. Test in the Extension Development Host (F5) against a NUKE repo lacking .fallout/; done means all acceptance checkboxes pass and the migration docs link is added.

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

描述

enhancement
Problem

Migrating a NUKE repo needs the Fallout.Migrate global tool and a terminal. People who open a NUKE repo in VS Code get an empty Fallout view and no hint what to do.

Outcome

The extension detects a NUKE build and offers to run fallout-migrate for them.

Acceptance criteria
  • Command Fallout: Migrate from NUKE… runs fallout-migrate --dry-run first, then the real run after the user confirms
  • Runs in the integrated terminal (the tool prompts) from the detected repo root
  • A NUKE repo (.nuke/, or Nuke.* in the build project) with no .fallout/ shows a one-time prompt to migrate; dismissible, remembered per workspace
  • Missing tool: offer dotnet tool install -g Fallout.Migrate
  • Tree refreshes after the migration finishes
  • Docs: link to Fallout docs/Migration/from-nuke.md
主要语言
C#
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

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

Fallout-build/Fallout.Extensions.VSCode 的其他 Issue

查看 Fallout-build/Fallout.Extensions.VSCode 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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