- Improved formatting for better readability.
- Adjusted heading styles and emphasis for clarity.
- Ensured consistency in the security vulnerability reporting instructions.
modified: .github/ISSUE_TEMPLATE/security_issue.yml
- 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/feature_request.yml
- 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
- 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/ask_for_help.yml
- Refined the template for better readability and conciseness.
- Enhanced formatting to improve clarity and accessibility.
- Used collapsible sections to streamline information presentation.
modified: .github/PULL_REQUEST_TEMPLATE.md
- Refined the language in the PULL_REQUEST_TEMPLATE.md for better clarity and consistency.
- Updated the wording of the "Related Issues" and "Additional Context" sections for improved understanding.
- Made the instructions more concise and easier to follow.
modified: .github/PULL_REQUEST_TEMPLATE.md
- Fixed a typo in the description for type: checkboxes, id: no-duplicate-question.
- Updated the URL query parameter from `?` to `?q` to ensure proper search functionality.
- Ensured that the description now links correctly to the list of existing issues.
modified: .github/ISSUE_TEMPLATE/ask_for_help.yml
- Updated the review guidlines with small improvements based on review feedback.
- Minor adjustments made to improve the clarity and readability of the guidelines.
- Refined phrasing and restructured sentences to align with better documentation practices.
- Removed redundant or unclear wording for a more concise explanation.
modified: .github/REVIEW_GUIDELINES.md
- Updated the pull request template with small improvements based on review feedback.
- Ensured clarity and consistency across the document.
modified: .github/PULL_REQUEST_TEMPLATE.md
- Added a 📝 emoji to the "Description" label for better visual clarity.
- The emoji was missing in the initial version, improving the user interface.
modified: .github/ISSUE_TEMPLATE/bug_report.yml
- Updated checkbox labels and descriptions to clarify instructions for verifying duplicate issues and agreeing to the security policy.
- Adjusted the wording in the "steps-to-reproduce" and "error-msg" sections for clarity.
- Enhanced deployment environment section to include more detailed instructions for setup.
- Improved overall formatting for readability and consistency.
modified: .github/ISSUE_TEMPLATE/ask_for_help.yml
- Improved the description of how to find related issues and pull requests.
- Added a direct link to the most recent issues and pull requests for better navigation.
- Reworded the "Security Policy" section to emphasize review and acknowledgment before reporting bugs.
- Adjusted the "Reproduction steps" and "Expected behavior" sections to ensure clear formatting.
- Enhanced placeholder text and descriptions for better user experience when reporting bugs.
modified: .github/ISSUE_TEMPLATE/bug_report.yml
- Updated the description for the "related-issues" section to include specific links for searching issues and pull requests.
- Enhanced clarity in the placeholder text for the "related-issues" section to provide better examples.
- Adjusted the formatting for consistent use of markdown and description clarity.
modified: .github/ISSUE_TEMPLATE/feature_request.yml
- 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
- Added a new section highlighting the importance of refraining from unnecessary pings to maintainers.
- Explained the reason behind this request to help maintainers focus on high-priority tasks.
- Updated the pull request template to reflect this change in the guidelines.
modified: .github/PULL_REQUEST_TEMPLATE.md
- Enhanced the pull request template for better clarity and organization.
- Updated sections for easier comprehension of the guidelines and checklist.
- Converted inline links to proper markdown format for better readability.
modified: .github/PULL_REQUEST_TEMPLATE.md
- Updated the links to the CONTRIBUTING.md file.
- Fixed the relative link to point to the correct location: `../CONTRIBUTING.md#project-styles`.
- Fixed the relative link to point to the correct location: `../CONTRIBUTING.md#coding-styles`.
modified: .github/REVIEW_GUIDELINES.md
- Updated the link to the pull request rules in the PULL_REQUEST_TEMPLATE.md file.
- Fixed the relative link to point to the correct location: `../CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma`.
modified: .github/PULL_REQUEST_TEMPLATE.md
- 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
- Reworded the note about pull request acceptance to improve clarity.
- Updated the phrasing to make the message more concise and user-friendly.
- Changed the link text for better accessibility and readability.
modified: .github/PULL_REQUEST_TEMPLATE.md
- Added a new `REVIEW_PROCESS.md` file outlining the guidelines for reviewing pull requests.
- The document aims to standardize the review process, ensuring consistency and improving code quality.
- It includes sections on preparation, general review, testing, security, performance, compliance, and more.
new file: .github/REVIEW_PROCESS.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 a section informing contributors about potential delays in feature requests and pull request reviews.
- Updated the template to clarify that feature requests and PR reviews may be delayed due to focus on bug fixes and performance improvements.
modified: .github/PULL_REQUEST_TEMPLATE.md
- 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
