chore: small doc/data update by @ex1234

[ex1234]

Automated small contribution. Thank you!

Summary by CodeRabbit

• Documentation
  • Updated the Contributing Guide with a minor tip (added in two places) to improve clarity for contributors.
  • Editorial-only change; no impact on features, performance, or APIs.
  • Helps new and existing contributors better understand recommended practices without altering any workflows.
  • No action required for end-users; purely informational improvement to project documentation.

[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

Adds two minor documentation notes in CONTRIBUTING.md. No code or behavior changes.

Changes

Cohort / File(s)	Summary
Docs CONTRIBUTING.md	Inserted minor note text ("Minor: doc tip from @ex1234") in two locations; editorial-only changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled the docs with a careful hop,
A tiny tip tucked in—then I stop.
No wires crossed, no logic to mend,
Just carrots of clarity I recommend.
Thump-thump! The guide’s now friendlier, friend. 🥕

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 title mentions a documentation update which aligns with the added notes in CONTRIBUTING.md but also references a “data update” that does not occur in this changeset, making it only partially accurate.
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

---

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

[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 df3b620 and ce47dae.

📒 Files selected for processing (1)

• CONTRIBUTING.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• CONTRIBUTING.md

🧠 Learnings (1)

📚 Learning: 2025-08-14T23:46:18.545Z

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.

Applied to files:

• CONTRIBUTING.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

[avelino]

Hi @ex1234, the automated checks for this PR failed. Please review the build logs and fix the issues. Specifically, the PR Quality Checks/quality-check failed. Please address this and re-request a review.