<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>代码评审 on PlumePHP</title><link>https://plumephp.com/tags/%E4%BB%A3%E7%A0%81%E8%AF%84%E5%AE%A1/</link><description>Recent content in 代码评审 on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Fri, 12 Jun 2026 16:20:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/%E4%BB%A3%E7%A0%81%E8%AF%84%E5%AE%A1/index.xml" rel="self" type="application/rss+xml"/><item><title>Godot 场景 Diff 评审工作流：让 .tscn 变更不再像盲盒</title><link>https://plumephp.com/godot-scene-diff-review-workflow-2026/</link><pubDate>Fri, 12 Jun 2026 16:20:00 +0800</pubDate><guid>https://plumephp.com/godot-scene-diff-review-workflow-2026/</guid><description>&lt;p&gt;Godot 的 &lt;code&gt;.tscn&lt;/code&gt; 文本格式是协作优势，也是评审难点。它能进 git，能做 diff，但真实 review 时经常像盲盒：一堆节点顺序变化、资源 id 重排、导出字段移动，reviewer 很难判断到底改了什么。尤其当关卡、美术和程序同时改一个场景，冲突解决就更痛苦。&lt;/p&gt;</description></item></channel></rss>