Update README.md

[noraegeorge]

This PR adds go-zero, an actively maintained cloud-native web and RPC framework for Go.

Why it’s a valuable addition:

• Widely used in production for scalable microservices.
• Built-in support for service discovery, RPC (via gRPC), circuit breaking, load shedding, and observability.
• Strong developer tooling (goctl) for code generation and API scaffolding.
• Actively maintained with 25k+ GitHub stars and a large contributor base.
• Complements existing frameworks like Gin and Fiber by focusing on reliability and large-scale distributed systems.

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

• [x ] I have read the Contribution Guidelines
• [ x] I have read the Maintainers Note
• [ x] I have read the Quality Standards

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

• [ x] The repo documentation has a pkg.go.dev link.
• [ x] The repo documentation has a coverage service link.
• [ x] The repo documentation has a goreportcard link.
• [ x] The repo has a version-numbered release and a go.mod file.
• [ x] The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• [ x] 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

• [x ] forge link (github.com, gitlab.com, etc): github.com
• [ x] pkg.go.dev: pkg link
• [x ] goreportcard.com: reportcard

Pull Request content

• [ x] The package has been added to the list in alphabetical order.
• [ x] The package has an appropriate description with correct grammar.
• [ x] 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:

• [x ] The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Added go-zero to the Web Frameworks section in the README.

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo link: missing
• pkg.go.dev: missing
• goreportcard: missing
• coverage: missing

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

[coderabbitai]

Walkthrough

A new entry for go-zero was added to the Web Frameworks section in README.md between Goyave and Hertz. This is a documentation-only addition with no code or functional changes.

Changes

Cohort / File(s)	Summary
Documentation Updates README.md	Added go-zero to the Web Frameworks list

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

hacktoberfest-accepted

Suggested reviewers

• phanirithvij
• bukarumar147

Poem

🐰 A frame for the web, so swift and so bright,
Between goyave and hertz, goes zero in sight!
The docs now are richer, the list now complete,
With go-zero added, the frameworks are neat! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	The pull request title "Update README.md" is vague and generic, providing no meaningful information about the specific nature of the update. While it technically refers to a real file being changed (README.md), the title fails to convey what was actually updated or why—it could describe virtually any modification to the README. A teammate scanning commit history would not understand that this PR adds a new framework (go-zero) to the Web Frameworks section. The title lacks the specificity needed to communicate the primary change.	To resolve this, the title should be more specific and descriptive, such as "Add go-zero to Web Frameworks list" or "Add go-zero framework to README." This would clearly communicate to reviewers and future readers what the main change entails without requiring them to investigate the actual changeset.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ 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.}

[noraegeorge]

created another PR to see if that will work

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90f89e3 and 55f8618.

📒 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). (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Codacy Static Code Analysis

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Keep the Web Frameworks list alphabetized.

Awesome-go requires alphabetical order inside each section. Here “go-zero” should come before “Goyave” (hyphen sorts before “y”), so please swap their positions.

Apply this diff:

-- [Goyave](https://github.com/go-goyave/goyave) - Feature-complete REST API framework aimed at clean code and fast development, with powerful built-in functionalities.
-- [go-zero](https://github.com/zeromicro/go-zero) - A web and RPC framework that integrates service discovery, fault tolerance, load shedding, circuit breaking, and code generation for cloud-native Go microservices.
+- [go-zero](https://github.com/zeromicro/go-zero) - A web and RPC framework that integrates service discovery, fault tolerance, load shedding, circuit breaking, and code generation for cloud-native Go microservices.
+- [Goyave](https://github.com/go-goyave/goyave) - Feature-complete REST API framework aimed at clean code and fast development, with powerful built-in functionalities.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- [Goyave](https://github.com/go-goyave/goyave) - Feature-complete REST API framework aimed at clean code and fast development, with powerful built-in functionalities.
	- [go-zero](https://github.com/zeromicro/go-zero) - A web and RPC framework that integrates service discovery, fault tolerance, load shedding, circuit breaking, and code generation for cloud-native Go microservices.
	- [Hertz](https://github.com/cloudwego/hertz) - A high-performance and strong-extensibility Go HTTP framework that helps developers build microservices.
	- [go-zero](https://github.com/zeromicro/go-zero) - A web and RPC framework that integrates service discovery, fault tolerance, load shedding, circuit breaking, and code generation for cloud-native Go microservices.
	- [Goyave](https://github.com/go-goyave/goyave) - Feature-complete REST API framework aimed at clean code and fast development, with powerful built-in functionalities.
	- [Hertz](https://github.com/cloudwego/hertz) - A high-performance and strong-extensibility Go HTTP framework that helps developers build microservices.

🤖 Prompt for AI Agents

In README.md around lines 3048 to 3050, the Web Frameworks list is not
alphabetized: "Goyave" appears before "go-zero"; reorder the entries so they are
in alphabetical order (case-insensitive, with hyphen considered before letters)
by moving the "go-zero" line above the "Goyave" line, keeping the exact entry
text and formatting otherwise unchanged.