|
| 1 | +## 🚀 OSCG'26 Contributor Notice |
| 2 | +**NexumDB participates in the Open Source Contributor Games 2026!** High-quality PRs earn you points, recognition, and networking opportunities. Please follow our [contribution guidelines](../CONTRIBUTING.md) for maximum impact and ensure your submission meets OSCG quality standards. |
| 3 | + |
1 | 4 | ## Summary |
2 | 5 | <!-- Provide a clear and concise description of what this PR changes and why it's needed --> |
3 | 6 |
|
@@ -60,15 +63,25 @@ Closes #(issue_number) <!-- Link related issues with "Closes #123" or "Fixes #45 |
60 | 63 | - [ ] Added/updated examples in `demo.sh` (if applicable) |
61 | 64 |
|
62 | 65 | ## Pre-Merge Checklist |
63 | | -- [ ] Self-reviewed my own code |
64 | | -- [ ] Added tests covering my changes |
| 66 | +- [ ] Self-reviewed my own code thoroughly |
| 67 | +- [ ] Added comprehensive tests covering my changes |
65 | 68 | - [ ] All existing tests pass locally |
66 | 69 | - [ ] Updated relevant documentation |
67 | 70 | - [ ] No uncommitted debug code or console logs |
68 | 71 | - [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/) |
69 | 72 | - [ ] Follows [Code of Conduct](CODE_OF_CONDUCT.md) |
70 | 73 | - [ ] Branch is up to date with `main` |
71 | 74 |
|
| 75 | +## 🎯 OSCG'26 Quality Standards |
| 76 | +By submitting this PR, I confirm: |
| 77 | +- [ ] I have read and follow the [CONTRIBUTING.md](../CONTRIBUTING.md) guidelines |
| 78 | +- [ ] My contribution meets OSCG'26 quality standards for production-ready code |
| 79 | +- [ ] I have tested my changes thoroughly across different scenarios |
| 80 | +- [ ] I understand the zero-tolerance policy for low-quality submissions |
| 81 | +- [ ] My code follows established patterns and maintains consistency |
| 82 | +- [ ] I have considered performance, security, and maintainability impacts |
| 83 | +- [ ] I acknowledge this project's participation in OSCG'26 and uphold its reputation |
| 84 | + |
72 | 85 | ## Additional Notes |
73 | 86 | <!-- Any additional context, deployment notes, follow-up tasks, or breaking changes details --> |
74 | 87 |
|
|
0 commit comments