fix: update issue template fields and Discord link

[mrT23]

PR Type

Enhancement, Documentation

---

Description

• Updated Discord community link in issue template configuration.

• Added optional labels to fields in miscellaneous issue template.

---

Changes walkthrough 📝

	Relevant files
Documentation	config.yml Update Discord community link in configuration                      .github/ISSUE_TEMPLATE/config.yml Updated the Discord community link to a new URL. +1/-1
Enhancement	miscellaneous.yml Add optional labels to miscellaneous fields                            .github/ISSUE_TEMPLATE/miscellaneous.yml Added "(optional)" to the Git provider label. Added "(optional)" to the System Info label. +2/-2

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
General	Use Discord invite link format Consider using an invite link format (discord.gg/...) instead of a direct channel link, as channel links may not work for users who haven't joined the server yet. .github/ISSUE_TEMPLATE/config.yml [9] -url: https://discord.com/channels/1057273017547378788/1126104260430528613 +url: https://discord.gg/your-invite-code Apply this suggestion Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies a critical usability issue - direct Discord channel links won't work for users who haven't joined the server, effectively blocking new users from accessing the community. Using an invite link is essential for proper Discord community access.	9

• Author self-review: I have reviewed the PR code suggestions, and addressed the relevant ones.