Enhance issue templates and documentation for better user guidance and contribution process.

[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 5 minutes and 53 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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 94f6046b-3593-43a6-8043-02d9ecf446fe

📥 Commits

Reviewing files that changed from the base of the PR and between 0d57ed5 and cae0add.

📒 Files selected for processing (3)

• PULL_REQUEST_TEMPLATE.md
• SUPPORT.md
• profile/README.md

📝 Walkthrough

Walkthrough

This PR standardizes GitHub community files: restructures the bug-report and feature-request templates (new/renamed fields), adds issue template config, adds CONTRIBUTING/SECURITY/SUPPORT docs, modernizes the PR template, and refreshes the profile README with package-listing and layout changes.

Changes

Cohort / File(s)	Summary
Issue templates & config .github/ISSUE_TEMPLATE/bug-report.yml, .github/ISSUE_TEMPLATE/feature-request.yml, .github/ISSUE_TEMPLATE/config.yml	Bug report: renamed description → steps-to-reproduce, added required expected-behavior and actual-behavior, added operating-system (optional), adjusted version placeholders/descriptions. Feature request: added proposed-solution, alternatives-considered, additional-context, reformatted fields/labels. Config: disables blank issues and adds contact links.
Community docs CONTRIBUTING.md, SECURITY.md, SUPPORT.md	Added CONTRIBUTING with dev setup, standards, testing, and PR process; SECURITY with private vulnerability reporting workflow and timeline; SUPPORT with help channels, package docs table, and sponsorship note.
Pull request template PULL_REQUEST_TEMPLATE.md	Replaced status table with a checklist (Breaking change, Bug fix, CI/build, Documentation, New feature, Refactoring) and added a "Related Issues" section.
Profile README profile/README.md	Refactored header and layout, rewrote philosophy section, renamed "The Toolset" → "Packages" and converted to a package table, added sponsor block and adjusted ecosystem attribution.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Add community health files, issue templates, and CI workflows for better project management. #2: Modifies the same issue templates and related community files; changes appear to overlap on template fields and structure.
• Remove outdated README.md content and update profile information. #1: Edits profile/README.md and related documentation formatting, likely overlapping with README/profile updates.

Poem

🐰 I hopped through templates, neat and bright,
I rewrote fields by soft lamplight,
Docs and guides now lined in rows,
Security doors and support that glows,
A tiny rabbit cheers—homegrown delight! 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: enhancing issue templates and documentation to improve user guidance and contribution processes, which aligns with all file modifications.
Description check	✅ Passed	The description is related to the changeset, correctly identifying this as a new feature with no bugfix or breaking changes, matching the nature of the documentation and template enhancements.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature_2

---

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