feat(docs): Add social media badge for following on X in README.md.

[terabytesoftw]

Pull Request

Q	A
Is bugfix?	❌
New feature?	✔️
Breaks BC?	❌

[coderabbitai]

Warning

Rate limit exceeded

@terabytesoftw has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 28 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between f2b91d3 and 3ed342e.

📒 Files selected for processing (1)

• CHANGELOG.md

📝 Walkthrough

Walkthrough

A changelog entry and new "Our social networks" section are added to document the introduction of a Follow on X badge in the README.

Changes

Cohort / File(s)	Summary
Documentation Enhancement CHANGELOG.md, README.md	Added changelog entry documenting the new X social media badge feature; introduced "Our social networks" section in README with Follow on X badge placement

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰✨ A badge of X now gleams so bright,
On README's page, in social light,
The changelog sings of networks new,
Follow along—we're connected to you! 🐦

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a social media badge for following on X in the README.md file.
Description check	✅ Passed	The description is directly related to the changeset, confirming this is a new feature that adds a social media badge to the README without breaking backward compatibility.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 5: Update the changelog entry "Enh 3: Add social media badge for
following on X in `README.md` (`@terabytesoftw`)" to match the project's numbering
convention by changing "Enh 3" to "Enh `#3`" so it follows the "Enh `#N`" format
used elsewhere in CHANGELOG.md.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e94388e and f2b91d3.

📒 Files selected for processing (2)

• CHANGELOG.md
• README.md

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: terabytesoftw
Repo: php-forge/foxy PR: 115
File: tests/Fallback/AssetFallbackTest.php:158-189
Timestamp: 2026-01-23T11:22:07.261Z
Learning: User terabytesoftw prefers not to use aliases when importing classes in PHP. They are comfortable with either fully-qualified class names or direct imports without aliases.

Learnt from: terabytesoftw
Repo: php-forge/support PR: 12
File: src/TestSupport.php:0-0
Timestamp: 2025-08-18T20:13:33.518Z
Learning: User terabytesoftw prefers clean trait-based designs over maintaining backward compatibility wrappers when refactoring utility classes in the php-forge/support project.

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 65
File: .github/workflows/composer-require-checker.yml:80-83
Timestamp: 2025-09-28T15:12:48.345Z
Learning: The user terabytesoftw prefers using floating tags like v1 for third-party actions in GitHub workflows instead of pinning to specific commit SHAs, even when it's a security best practice to pin to immutable commits.

⏰ 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: linter / Super Linter
• GitHub Check: linter / Super Linter

🔇 Additional comments (1)

README.md (1)

167-169: Looks good.

Badge and section placement read cleanly and match the stated PR objective.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}