Added Go by Example

[stjepanjurekovic]

Hi,

Stjepan from Manning here. I think this title would be a great match for your list. Thank you for considering it.

Best,

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):
• pkg.go.dev:
• goreportcard.com:
• coverage service link (codecov, coveralls, etc.):

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
  • Expanded the “Where to discover new Go libraries” list with “Go by Example: Programmer's guide to idiomatic and testable code,” highlighting idiomatic, testable practices through real programs.
  • Positioned the new entry between “Go in Practice, Second Edition” and “Know Go: Generics,” shifting subsequent items.
  • Improves resource discoverability and guidance for learning best practices.

[coderabbitai]

Walkthrough

Added a single documentation update to README.md: a new entry in the “Where to discover new Go libraries” list, inserting “Go by Example: Programmer's guide to idiomatic and testable code” with a brief description, positioned between existing list items.

Changes

Cohort / File(s)	Summary
Docs update README.md	Inserted a new list item linking to “Go by Example: Programmer's guide to idiomatic and testable code” with a descriptive blurb; subsequent items shifted down accordingly.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• phanirithvij
• bukarumar147

Poem

I nibbled the docs with a careful bite,
A shiny new link in the library light.
Hop, hop—resources now neatly aligned,
Breadcrumbs for Go-folks, thoughtfully assigned.
With twitching whiskers, I press “merge”—delight! 🥕

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• 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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Thank you for contributing to awesome-go. We will review your contribution as soon as possible.

Make sure you add the links in the body of the pull request that are requested in the contribution guide:

• repo link
• pkg.go.dev
• goreportcard.com
• coverage

Your project is under review. It may take a few days to be approved.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

README.md (2)

3512-3515: Place the new entry in alphabetical order within “E-books for purchase”.

This section is alphabetically sorted by title. “Go by Example …” should come before “Go in Practice, Second Edition”.

Apply this reorder:

- - [Go in Practice, Second Edition](https://www.manning.com/books/go-in-practice-second-edition)  - Your practical guide on the ins-and-outs of Go development, covering the standard library and the most important tools from Go’s powerful ecosystem.
- - [Go by Example: Programmer's guide to idiomatic and testable code](https://www.manning.com/books/go-by-example)  - A book that unpacks real Go programs to highlight the language features and idiomatic coding practices used by the pros.
+ - [Go by Example: Programmer's guide to idiomatic and testable code](https://www.manning.com/books/go-by-example)  - A book that unpacks real Go programs to highlight the language features and idiomatic coding practices used by the pros.
+ - [Go in Practice, Second Edition](https://www.manning.com/books/go-in-practice-second-edition)  - Your practical guide on the ins-and-outs of Go development, covering the standard library and the most important tools from Go’s powerful ecosystem.

---

3513-3513: Avoid name confusion with the existing “Go by Example” tutorial entry.

There’s already a “Go By Example” tutorial listed under Websites/Tutorials. Confirm this new book entry is distinct and that the title/description are sufficient to disambiguate. If needed, tweak the description to explicitly mention it’s a Manning book to reduce confusion.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between db6f5ef and fae6a3f.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: elymanuba
PR: avelino/awesome-go#5762
File: README.md:0-0
Timestamp: 2025-08-14T23:46:18.545Z
Learning: When reviewing contributions to the awesome-go repository, maintain a relaxed and less pedantic approach. Users may find overly strict feedback about formatting, alphabetical ordering, or description tone to be unnecessary. Focus on major issues rather than minor stylistic preferences.

⏰ 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