Add go-zero to Web Frameworks section

[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
• [ x] pkg.go.dev: pkg link
• [ x] goreportcard.com: reportcard
• [ x] coverage service link: It shows a Codecov badge in the README

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 framework entry to the Web Frameworks section in README with project link and description.

[coderabbitai]

Walkthrough

A new entry for go-zero is added to the Web Frameworks section in README.md, including a project link and description. No functional logic or behavior is modified.

Changes

Cohort / File(s)	Summary
Documentation Updates README.md	Added go-zero web framework entry to the Web Frameworks section with project link and description

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

The change is a straightforward documentation addition affecting a single file with no logic modifications or interdependencies to evaluate.

Suggested reviewers

• phanirithvij
• bukarumar147
• Ki-er

Poem

🐰 A framework joins the README's hall of fame,
go-zero takes its place with well-deserved name,
One entry added, neat and clean and bright,
Documentation sparkles—a simple, perfect sight! ✨

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 pull request title "Add go-zero to Web Frameworks section" directly and accurately describes the primary change in the changeset. The main modification is adding a new entry for the go-zero framework to the Web Frameworks section of README.md, which is exactly what the title states. The title is concise, specific, and avoids vague or generic terminology. A teammate scanning the repository history would immediately understand that this PR introduces the go-zero framework to the documentation.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d69a583 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). (1)

• GitHub Check: Codacy Static Code Analysis

---

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

[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.

[noraegeorge]

please accept my contribution