Update README.md

[RohitKattimani]

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/PaulSonOfLars/gotgbot
• pkg.go.dev: https://pkg.go.dev/github.com/PaulSonOfLars/gotgbot/v2
• goreportcard.com: https://goreportcard.com/report/github.com/PaulSonOfLars/gotgbot
• 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.

Thanks for your PR, you're awesome! 😎

Summary by CodeRabbit

• Documentation
  • Added a new library entry, gotgbot, to the Bot Building section. This notes an autogenerated Go wrapper for the Telegram API, providing developers with an additional option when selecting tooling for bot development.
  • Content-only update; no changes to application behavior or functionality.

[coderabbitai]

Walkthrough

Documentation update adding a new library entry (gotgbot) to the Bot Building section in README.md.

Changes

Cohort / File(s)	Summary
Docs update README.md	Added gotgbot library entry under Bot Building; content-only change with no code modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• phanirithvij
• MihailCugorka

Poem

Hop hop! I nibble on docs so neat,
A new bot wrapper—what a treat!
In README fields I plant a note,
gotgbot sails—update afloat.
Carrots checked, links aligned—sweet! 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The title “Update README.md” is overly generic and does not convey the primary change of adding the gotgbot library entry to the Bot Building section, making it difficult for collaborators to understand the intent at a glance.	Please update the title to something more specific, for example “Add gotgbot Telegram API wrapper to Bot Building section in README,” so that the main change is immediately clear to reviewers.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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 8cb5e86 and a458f7b.

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ 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: quality

---

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: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: missing

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

[avelino]

Please include the pkg.go.dev, Go Report Card and coverage links in the PR description, and make sure the project meets the history/release/CI requirements. After that, we’ll be happy to merge it.

[avelino]

Hi @RohitKattimani, the automated checks for this PR failed. Please review the build logs and fix the issues. Specifically, the tests/Running test check failed. Please address this and re-request a review.