Skip to content

Conversation

YaroslavPodorvanov
Copy link
Contributor

@YaroslavPodorvanov YaroslavPodorvanov commented Aug 12, 2025

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

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

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
    • Updated README Websites section with a new ReadyToTouch entry, linking to its GitHub repo and highlighting real-world Go usage (companies and jobs) via readytotouch.com.
    • Positioned the entry alongside existing resources for easier discovery and improved clarity.
    • No code changes; functionality and behavior remain unaffected.

Copy link

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.

Copy link
Contributor

coderabbitai bot commented Aug 12, 2025

Walkthrough

Added a new entry “ReadyToTouch” under the Websites section in README.md, linking to its GitHub repo and referencing production Go usage via readytotouch.com. No code or API changes.

Changes

Cohort / File(s) Summary
Documentation
README.md
Inserted “ReadyToTouch” website entry between pkg.go.dev and studygolang, linking to its GitHub repo and noting production Go usage via readytotouch.com.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • phanirithvij
  • bukarumar147

Poem

I nibbled the docs with gentle touch,
A link now hops—just one, not much.
Between the lines I leave a trace,
ReadyToTouch takes its place.
Ears up high, I thump with cheer—
Small hop today, the path is clear. 🐇✨

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
README.md (1)

3698-3698: Prefer linking to the website itself and minimize deep links.

In the Websites section we usually point the item to its primary website and keep descriptions free of extra links. This reduces link-check noise and stays consistent with surrounding entries.

Apply this diff:

- - [ReadyToTouch](https://github.com/readytotouch/readytotouch) - Open-source list of [companies](https://readytotouch.com/golang/companies) and [jobs](https://readytotouch.com/golang/jobs) using Go in production.
+ - [ReadyToTouch](https://readytotouch.com/golang/) - Open-source list of companies and jobs using Go in production.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 357d59c and d765976.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
README.md (1)
main_test.go (1)
  • goqueryFromReadme (34-48)
⏰ 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
🔇 Additional comments (2)
README.md (2)

3698-3699: Alphabetical placement and copy look good.

The entry is correctly placed between pkg.go.dev and studygolang, and the description is concise.


3698-3698: All ReadyToTouch links return HTTP 200
I ran curl -L on the three URLs and confirmed they all resolve with a 200 status (root → /golang/companies, /golang/companies, /golang/jobs). No updates to the README are needed.

@avelino
Copy link
Owner

avelino commented Oct 7, 2025

Missing: SemVer release (0 tags - requires at least one vX.Y.Z), pkg.go.dev badge, Go Report Card badge, coverage badge, CI setup, and badge links in PR body.

@YaroslavPodorvanov
Copy link
Contributor Author

This is not a Go library, but an open-source website ( https://readytotouch.com/golang/companies ).
Therefore, badges like pkg.go.dev, Go Report Card, coverage, or SemVer releases do not apply.
Please confirm if it still fits the "awesome-go" guidelines as a community resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants