From 83b03dd766ace6d22acac8254b69637748de5bbf Mon Sep 17 00:00:00 2001 From: GJS Date: Wed, 2 Apr 2025 05:48:24 +0200 Subject: [PATCH] Updated: Improved bug_report.yml with guidelines for pinging maintainers - Added a new section with clear guidelines on when and when not to ping maintainers. - Improved readability with a structured format for better comprehension. - Applied minor Markdown adjustments for consistency and clarity. modified: .github/ISSUE_TEMPLATE/bug_report.yml --- .github/ISSUE_TEMPLATE/bug_report.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index c9dbbd193..443ed3c6b 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -8,13 +8,20 @@ body: - type: markdown attributes: value: | - ## **❗ Important: Please Avoid Unnecessary Pinging of Maintainers** + ## ❗ Important Announcement + + ### 🚫 Please Avoid Unnecessary Pinging of Maintainers **We kindly ask users to refrain from pinging maintainers unless absolutely necessary. Pings should be reserved for critical issues or urgent matters that require immediate attention.** - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention. - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer. + #### Guidelines for Pinging + + - ✅ **Appropriate**: Critical issues or urgent matters requiring immediate attention. + - ❌ **Not Appropriate**: Repeated or non-urgent pings, which may be ignored or addressed later. + - type: textarea id: related-issues validations: