# 🎉 Welcome to Zedis! / 欢迎贡献 Zedis!

## 🇬🇧 English
Thank you for taking the time to contribute to Zedis! 🦀

> ⚠️ **IMPORTANT CONTRIBUTING GUIDELINES:**
> 1. **New Features:** Before writing code for a new feature, **please open an Issue first** to discuss it. This ensures it aligns with our roadmap and saves your time!
> 2. **Typos & Grammar:** Please **DO NOT** open PRs *solely* for fixing minor typos, formatting, or grammar issues in documentation/comments. We prefer to batch these or fix them alongside larger code changes.

To help us review your Pull Request efficiently, please provide the following information.

### Description
### Type of Change
- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
- [ ] ✨ New feature (I have opened an Issue and discussed it beforehand)
- [ ] 🛠️ Refactoring / Tech debt (changes to internal architecture or performance)
- [ ] 📝 Documentation / i18n update

### Developer Checklist
- [ ] I have run `cargo fmt` to format the code.
- [ ] I have run `cargo clippy` and resolved any warnings.
- [ ] My code builds and runs successfully.
- [ ] ⚖️ **I have read and agree to the [Zedis Contributor License Agreement](CLA.md), confirming my contribution is original and licensed under the project's open-source terms.**
- [ ] (Optional) I have tested this on: [ ] macOS / [ ] Windows / [ ] Linux.
---

## 🇨🇳 中文
感谢你为 Zedis 贡献代码！🦀

> ⚠️ **重要贡献指南：**
> 1. **关于新特性：** 在编写新功能的代码前，**请务必先提交 Issue 进行讨论**，以确保其符合项目规划，避免浪费你的精力！
> 2. **关于拼写与语法：** 请 **不要** 提交仅仅为了修复文档/注释中个别拼写、格式或语法错误的 PR。我们倾向于集中批量处理这些小问题，或者在提交较大功能代码时顺手修复。

为了帮助我们更高效地进行 Code Review，请提供以下信息。

### 变动描述
### 变动类型
- [ ] 🐛 Bug 修复 (修复现有问题的非破坏性修改)
- [ ] ✨ 新特性 (我已提前提交 Issue 并经过了讨论和评估)
- [ ] 🛠️ 代码重构 / 性能优化 (底层架构调整，不影响外部行为)
- [ ] 📝 文档完善 / 多语言 (i18n) 更新

### 开发者自查表
- [ ] 我已运行 `cargo fmt` 格式化代码。
- [ ] 我已运行 `cargo clippy` 并修复了所有警告。
- [ ] 我的代码可以在本地成功编译并运行。
- [ ] ⚖️ **我已阅读并同意 [Zedis 贡献者许可协议](CLA.md)，确认我的贡献为原创，并授权在项目的开源协议下使用。**
- [ ] (可选) 我已在以下平台进行过测试： [ ] macOS / [ ] Windows / [ ] Linux。