Now vibe coding, so learning hammer FE ?https://channel.meo-ai.comhttps://channel.meo-ai.com/posts/664https://channel.meo-ai.com/posts/664Sat, 20 Jun 2026 09:52:46 GMT<span class="post-title-source">《Git_Worktree_是什么以及为什么现在应该使用它》</span><br /><br />标签：<a href="/search/result?q=%23Git" title="#Git">#Git</a> <a href="/search/result?q=%23GitHubCopilot" title="#GitHubCopilot">#GitHubCopilot</a> <a href="/search/result?q=%23Worktree" title="#Worktree">#Worktree</a> <a href="/search/result?q=%23%E4%B8%8A%E4%B8%8B%E6%96%87%E5%88%87%E6%8D%A2" title="#上下文切换">#上下文切换</a> <a href="/search/result?q=%23AI_%E5%B9%B6%E8%A1%8C%E5%BC%80%E5%8F%91" title="#AI_并行开发">#AI_并行开发</a><br /><br />总结：<br />Git Worktree 是 Git 2015 年就已内置的功能，但最近因 <mark class="highlight">AI</mark> 时代并行开发需求激增而重新流行。它允许你在同一仓库的不同分支上同时工作，每个分支拥有独立的文件夹，彻底告别 stash 切换和编辑器上下文中断的烦恼。GitHub Copilot 应用已将其作为默认工作模式。<br /><br />文章要点：<br />1. 告别 stash 地狱：紧急修 bug 时再也不用 stash 当前工作、切分支、修完再切回来 pop stash 了，Worktree 让你原地不动就能开新窗口干活<br />2. 每个分支一个文件夹：用 <code>git worktree add</code> 瞬间创建基于任意分支的独立工作目录，原编辑器窗口完全不受影响，真正实现并行开发<br />3. <mark class="highlight">AI</mark> 时代让它翻红：以前 Worktree 鲜为人知，现在因为 <mark class="highlight">AI</mark> Agent 和人类开发者需要大量并行会话，它成了 GitHub Copilot 等工具的默认模式<br />4. 注意几个小坑：每个 Worktree 都要独立装依赖（磁盘会胖）、文件夹要记得清理、同一分支不能同时在两个 Worktree 检出<br />5. VS Code 和 Copilot 都原生支持：不需要记命令，图形界面里直接选"New worktree"就能用，路径和变更状态一目了然<br /><br />URL：<a href="https://github.blog/ai-and-ml/github-copilot/what-are-git-worktrees-and-why-should-i-use-them/" target="_blank" rel="noopener" title="https://github.blog/ai-and-ml/github-copilot/what-are-git-worktrees-and-why-should-i-use-them/">https://github.blog/ai-and-ml/github-copilot/what-are-git-worktrees-and-why-should-i-use-them/</a><a class="tgme_widget_message_link_preview" href="https://github.blog/ai-and-ml/github-copilot/what-are-git-worktrees-and-why-should-i-use-them" target="_blank" rel="noopener" title="Git worktrees have been around since 2015, but it wasn't until recently they became popular. Learn what they are, how to use them, and why you might."> <div class="link_preview_site_name accent_color">The GitHub Blog</div> <img class="link_preview_image" alt="What are git worktrees, and why should I use them?" src="/static/https://cdn4.telesco.pe/file/NVbaeYKKRwStd4oVEyZ9rXmgW5gE5CKYe1EQHLTMcLsfSAC0kRdnUenj9FnM3wD0lcDnqvLhSAfBEd5Y8DajuvB0TNs7E_3i9cuzpYMvnHD4OsblwYvt2Mv11V9hIweaDJ0Uzrbo9RJmfhJt17mHKBvn6bZubWO83GMTtI3oo2LobtaSKX1rBmd1o_ivPqsi5UNh7VjHkebQYB-9K20pevbVS_T7OgOWXjLXAAkXsNer4IldHsC_rdO2z2_VKW0w5LBr7-fP3Yu6lDGQLrZY5SRxtBxSANPidJOGrOqD9PG7ebfxW6GHtspXDVbb1X36mlLOv6udrKWxABI-CellTA.jpg" width="1200" height="630" loading="eager" /> <div class="link_preview_title">What are git worktrees, and why should I use them?</div> <div class="link_preview_description">Git worktrees have been around since 2015, but it wasn't until recently they became popular. Learn what they are, how to use them, and why you might.</div> </a>