[codex] add Discord community links

[andrewtdiz]

Summary

Adds the Perry Discord invite to the top of the README as a visible community badge/link.

Adds the Discord invite to the GitHub issue chooser so community questions have an obvious place to go.

Test plan

• git diff --check
• ruby -e 'require "yaml"; YAML.load_file(".github/ISSUE_TEMPLATE/config.yml"); puts "YAML OK"'

Summary by CodeRabbit

• Documentation

  • Added Discord community badge and invitation link to the README.

• Chores

  • Updated issue template configuration to include Discord community contact option.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a7a9358d-65b0-4538-9b0e-f81796432129

📥 Commits

Reviewing files that changed from the base of the PR and between 9b6bbe0 and 1b12070.

📒 Files selected for processing (2)

• .github/ISSUE_TEMPLATE/config.yml
• README.md

---

📝 Walkthrough

Walkthrough

This PR adds Discord community links to the Perry project in two places: the GitHub issue template configuration now includes a "Join the Perry Discord" contact link, and the README includes a community badge and link in its introductory section. Both changes point to the same Discord server and serve to improve project discoverability for contributors and users.

Changes

Community Discord Links

Layer / File(s)	Summary
Community Discord links .github/ISSUE_TEMPLATE/config.yml, README.md	Issue template configuration updated with a Discord contact link, and README enhanced with a community badge and link to the Perry Discord server in the introductory section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A Discord door opens wide,
Where Perry's community may reside,
In config and README, links now shine,
Bringing friends to chat and align! 💜

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes a summary and test plan but omits required sections like 'Changes', 'Related issue', and the checklist.	Add a bulleted 'Changes' section listing the files modified, specify 'Related issue' or mark as 'n/a', and include the required checklist with acknowledgments.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately summarizes the main changes: adding Discord community links to the repository.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}