fix: remove shell rendering from issue templates

[ofir-frd]

PR Type

Bug fix, Documentation

---

Description

• Removed render: shell attribute from issue templates.

• Simplified bug report and miscellaneous templates for clarity.

---

Changes walkthrough 📝

Relevant files

Bug fix

bug-report.yml Removed `render: shell` from bug report template                  .github/ISSUE_TEMPLATE/bug-report.yml Removed render: shell attribute from system-info field. Removed render: shell attribute from bug-details field. +0/-2      miscellaneous.yml Removed `render: shell` from miscellaneous template            .github/ISSUE_TEMPLATE/miscellaneous.yml Removed render: shell attribute from system-info field. Removed render: shell attribute from issues-details field. +0/-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	Add markdown rendering for content Consider adding a specific render format (like 'markdown') to the bug-details textarea to ensure proper formatting of user-submitted content, especially for error messages and logs. .github/ISSUE_TEMPLATE/bug-report.yml [31-38] - type: textarea id: bug-details attributes: label: Bug details description: Please describe the problem. placeholder: Describe the problem + render: markdown validations: required: true Apply this suggestion Suggestion importance[1-10]: 4 Why: Adding 'render: markdown' could improve the readability of user-submitted bug reports, especially for code blocks and error messages. However, the PR is explicitly removing render attributes, suggesting a deliberate choice to use default rendering.	4

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