Add NoKV to Database section

[feichai0017]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/feichai0017/NoKV
• pkg.go.dev: https://pkg.go.dev/github.com/feichai0017/NoKV
• goreportcard.com: https://goreportcard.com/report/github.com/feichai0017/NoKV
• coverage service link (codecov, coveralls, etc.): https://app.codecov.io/gh/feichai0017/NoKV

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.
• I removed the following packages around my addition: (please give a short reason for each removal)

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Added NoKV database reference to the documented databases list, highlighting its high-performance distributed KV storage capabilities based on LSM Tree architecture.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new database entry for NoKV, a high-performance distributed KV storage system based on LSM Tree, was added to the "Databases Implemented in Go" section of the README with its corresponding GitHub repository link.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Added NoKV entry to "Databases Implemented in Go" section with repository URL and description

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A new database joins the fold,
NoKV's story starts to unfold,
LSM trees with speed so grand,
In README's list, it takes its stand!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add NoKV to Database section' directly and clearly describes the main change - adding a new entry to the Database section of the README.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR adds NoKV, a distributed key-value storage system, to the Database section of the awesome-go list. The addition follows the repository's contribution guidelines by including proper documentation links and meeting quality standards.

Key Changes:

• Adds NoKV entry to the Database section in alphabetical order between "moss" and "nutsdb"

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

760-760: Neutralize tone and align terminology with list style.

Avoid promotional wording and expand abbreviations for consistency. Suggest:

- - [NoKV](https://github.com/feichai0017/NoKV) - A high-performance distributed KV storage based on LSM Tree.
+ - [NoKV](https://github.com/feichai0017/NoKV) - Distributed key-value store based on an LSM tree.

As per coding guidelines.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6baf327 and 36b4c9d.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Cleanup artifacts
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Seer Code Review
• GitHub Check: quality

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

These checks are a best-effort automation and do not replace human review.