Fix typo in issue template

[davet2001]

Description

Fix minor typo I spotted

Motivation and Context

How has this been tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[coderabbitai]

📝 Walkthrough

Walkthrough

A single typo fix in .github/ISSUE_TEMPLATE/config.yml: corrected “dicussion” to “discussion” in a contact_links about field. No functional, structural, or exported entity changes.

Changes

Cohort / File(s)	Summary
Issue templates .github/ISSUE_TEMPLATE/config.yml	Corrected a misspelling in the contact_links about text (“dicussion” → “discussion”).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

documentation

Suggested reviewers

• frenck

Poem

A hare with keen editorial vision,
hopped through YAML with tidy precision.
Swapped “dicussion” for “discussion”—hurray!
Fewer typos to lead folks astray.
Thump-thump, I stamp with gentle cheer,
clean carrots of text, crispy and clear. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly and accurately describes the main change of the pull request, which is correcting a typo in the issue template, without unnecessary detail or unrelated content.
Description Check	✅ Passed	The pull request description briefly states the purpose of the change as fixing a minor typo, which is directly relevant to the content of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e3e8602 and 8feaede.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/config.yml (1 hunks)

🔇 Additional comments (1)

.github/ISSUE_TEMPLATE/config.yml (1)

5-5: Typo correction confirmed

The wording now matches the correct spelling and keeps the guidance clear.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud