📄 中文摘要
最近，合并请求描述中新增了一条规则，要求必须包含“## 背景”部分。该部分旨在阐明更改的原因、方法和权衡，提供更全面的上下文信息。尽管这一规则合理且易于遵循，但其来源却不明，可能是因为某人对缺少背景信息的合并请求感到沮丧，或团队在讨论审查流程时发现了这一空白。无论规则的形成过程如何，当前的情况是，规则存在，但相关讨论却不可得。
我未参与的会议
发布: 2026年3月25日
📄 English Summary
The meeting I wasn't in
A new rule has been introduced in merge request descriptions, requiring a '## Context' section. This section aims to clarify the reasons, methods, and trade-offs associated with changes, providing a comprehensive context. While the rule is logical and easy to follow, its origin remains unclear. It may have arisen from someone’s frustration with merge requests lacking context, or from team discussions identifying gaps in the review workflow. Regardless of how the rule was established, it exists without the accompanying discussion.