<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Conventional Commits - Naifan Li's Blog</title><link>https://blog.omagiclee.com/tags/conventional-commits/</link><description>Conventional Commits - Naifan Li's Blog</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.omagiclee.com/tags/conventional-commits/index.xml" rel="self" type="application/rss+xml"/><item><title>Git Commit 规范：提交语义、变更边界与合并校验</title><link>https://blog.omagiclee.com/posts/toolkits/github/commit-conventions/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0800</pubDate><guid>https://blog.omagiclee.com/posts/toolkits/github/commit-conventions/</guid><description>&lt;p>Commit 规范应同时明确提交语义、变更边界和兼容性影响，为代码评审、回归定位与版本发布提供依据。&lt;/p>
&lt;p>本文以 Conventional Commits 1.0.0 为格式基础，结合 Data Flywheel 项目讨论提出实施约定。标准要求与团队策略分别标明；项目策略为建议方案，示例不代表真实提交。&lt;/p></description></item></channel></rss>