- Updated descriptions and placeholders for clearer instructions and consistency.
- Fixed minor formatting and content issues to better align with documentation standards.
- Enhanced the "Deployment Environment" section to offer better guidance for users.
modified: .github/ISSUE_TEMPLATE/bug_report.yml
- Updated the descriptions and placeholders for better clarity and accuracy.
- Fixed minor formatting issues to align with current documentation standards.
- Added more detailed explanations in the deployment environment section for better user guidance.
modified: .github/ISSUE_TEMPLATE/ask_for_help.yml
- Renamed the file `REVIEW_PROCESS.md` to `REVIEW_GUIDELINES.md` for clarity.
- Made small adjustments to `PULL_REQUEST_TEMPLATE.md` and `feature_request.yml`
to link to the newly renamed `REVIEW_GUIDELINES.md`.
- Updated references to the review process throughout relevant files.
modified: .github/ISSUE_TEMPLATE/feature_request.yml
modified: .github/PULL_REQUEST_TEMPLATE.md
renamed: .github/REVIEW_PROCESS.md -> .github/REVIEW_GUIDELINES.md
- Renamed `feature_request.yaml` to `feature_request.yml` to follow project conventions.
- Updated the description in the markdown content to reflect a temporary delay in feature requests and PR reviews.
- Adjusted the labels and body content to better communicate the status of new feature requests.
- Minor revisions in the markdown to enhance clarity and improve the user experience.
renamed: .github/ISSUE_TEMPLATE/feature_request.yaml -> .github/ISSUE_TEMPLATE/feature_request.yml
- Renamed the file `bug_report.yaml` to `bug_report.yml` for consistency with standard YAML file extensions.
- Changed the label from `P2-moderate` to `P2-medium` in the file for better alignment with naming conventions.
renamed: .github/ISSUE_TEMPLATE/bug_report.yaml -> .github/ISSUE_TEMPLATE/bug_report.yml
- Renamed the file from `ask-for-help.yaml` to `ask_for_help.yml` to adhere to consistent naming conventions.
- This improves consistency and avoids potential issues with file naming conventions in different environments.
renamed: .github/ISSUE_TEMPLATE/ask-for-help.yaml -> .github/ISSUE_TEMPLATE/ask_for_help.yml
- Added "P1: high" label to security issues for better prioritization.
- Updated markdown instructions to emphasize the importance of using GitHub Security Advisory for reporting vulnerabilities.
- Clarified that this issue is solely for sharing the advisory URL and not for discussing the vulnerability details.
- Retained the step-by-step guide for submitting and sharing the GitHub Security Advisory URL.
modified: .github/ISSUE_TEMPLATE/security_issue.yml
- Temporarily suspended the acceptance of new feature requests to focus on bug fixes, performance improvements, and critical updates.
- Added a markdown section notifying users about the temporary suspension and the backlog status of existing requests.
- Introduced a checkbox to confirm user understanding of the feature request suspension.
- Enhanced the feature request template with a section about the policy on unnecessary pings to maintainers, including an acknowledgment checkbox.
- Updated labels to include "P4: negligible" and "backlog" for better issue categorization.
modified: .github/ISSUE_TEMPLATE/feature_request.yaml
- Added a markdown section to discourage unnecessary pings to maintainers, ensuring focused responses to urgent issues.
- Introduced a checkbox to confirm understanding of the new pinging policy.
- Updated the labels and assignees to improve issue categorization and accountability.
- Streamlined the bug report process by making related issues search and explanation more prominent.
- Enhanced the security policy section to ensure users acknowledge reading it before submitting security-related bugs.
- Made minor adjustments to field descriptions for clarity and ease of use.
modified: .github/ISSUE_TEMPLATE/bug_report.yaml
- Added a new section to discourage unnecessary pings to maintainers, ensuring better focus on high-priority tasks.
- Introduced a checkbox to acknowledge understanding of the new pinging guidelines.
- Streamlined issue submission process by emphasizing the importance of checking for duplicate issues before submitting.
- Enhanced security policy section to ensure users agree to review it before reporting security-related issues.
- Reorganized the template for clearer communication and improved user engagement.
modified: .github/ISSUE_TEMPLATE/ask-for-help.yaml
