chore: auto-assign all new issues to Xerrion

[Xerrion]

Description

Adds �ssignees: [Xerrion] to all issue form templates so every new issue is automatically assigned.

Type of Change

• Documentation update

Related Issues

N/A

Testing

• Luacheck passes (luacheck .)

Checklist

• My commits follow conventional commit format

Summary by CodeRabbit

• Chores
  • Updated GitHub issue template configurations to automatically assign new bug reports and feature requests.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 48fe46e1-6863-4ef9-8187-eb970bd36742

📥 Commits

Reviewing files that changed from the base of the PR and between abf3ee6 and 476a3ba.

📒 Files selected for processing (2)

• .github/ISSUE_TEMPLATE/bug-report.yml
• .github/ISSUE_TEMPLATE/feature-request.yml

---

📝 Walkthrough

Walkthrough

Two GitHub issue templates were updated to assign newly created issues to Xerrion. The bug report template received an assignees field with Xerrion as the assignee, while the feature request template had its existing empty assignees field populated with Xerrion.

Changes

Cohort / File(s)	Summary
GitHub Issue Templates .github/ISSUE_TEMPLATE/bug-report.yml, .github/ISSUE_TEMPLATE/feature-request.yml	Added or updated assignees field to assign new issues to Xerrion instead of leaving unassigned or empty.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

ci

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'chore: auto-assign all new issues to Xerrion' follows Conventional Commit format with valid type 'chore' and clearly describes the main change: automatically assigning new issues.
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.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}