chore: sync organization templates #1
Conversation
Updated from organization .github repository: - .github/ISSUE_TEMPLATE/bug_report.yaml - .github/ISSUE_TEMPLATE/config.yml - .github/ISSUE_TEMPLATE/feature_request.yaml - .github/ISSUE_TEMPLATE/security_report.yaml - .github/ISSUE_TEMPLATE/support_question.yaml - .github/PULL_REQUEST_TEMPLATE/pr_form.yml - .github/PULL_REQUEST_TEMPLATE/pull_request_template.md - .github/workflows/pr_checks.yml - .github/workflows/commit-msg-validation.yml - SECURITY.md This PR was automatically generated to keep repository templates in sync with organization standards.
🤖 PR Validation ReportSummary
Detailed Results
💡 Tip: Consider addressing the warnings above to improve your PR quality. This check validates PR title format and ensures all required sections are present in the PR description. |
🤖 Commit Message Validation ReportSummary
Commit Details
This check validates that all commit messages follow conventional commit format. |
Summary of ChangesHello @BadRat-in, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request is an automated synchronization of essential repository configuration files, including issue and pull request templates, and a security policy. The primary goal is to maintain consistency and alignment with organization-wide development and community health standards across all repositories. This ensures a standardized approach to reporting issues, submitting code, and handling security concerns. Highlights
Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request automatically syncs organization-wide templates, which is a good practice for maintaining consistency. My review of the new templates has identified a few issues. Most importantly, the security report template contains a placeholder email address, which is a critical issue that could prevent security vulnerabilities from being reported correctly. I've also found a broken link in the issue configuration file and some formatting problems in the markdown pull request template. I've provided suggestions to fix these issues to ensure the templates are correct and usable.
| value: | | ||
| **Security disclosure instructions** | ||
| * Do NOT post exploits, PII, credentials, or sensitive attachments in a public issue. | ||
| * If you have sensitive details, email: security@ORG-DOMAIN (or use our private disclosure process) — see SECURITY.md. |
There was a problem hiding this comment.
The email address security@ORG-DOMAIN is a placeholder and needs to be replaced with the actual security contact email. According to the SECURITY.md file, the correct email is security@rkinnovate.com. Using a placeholder here is critical as it could prevent security vulnerabilities from being reported to the correct channel.
* If you have sensitive details, email: security@rkinnovate.com (or use our private disclosure process) — see SECURITY.md.| url: https://github.com/RKInnovate/.github/blob/main/SECURITY.md | ||
| about: "Report security vulnerabilities (private channel). Use this for sensitive security issues only." | ||
| - name: General support | ||
| url: https://github.com/RKInnovate/.github/ISSUE_TEMPLATE#support--questions |
There was a problem hiding this comment.
The URL provided for 'General support' appears to be broken as it leads to a 404 page. This could confuse users trying to find the correct template for support questions. Please update this to a valid URL. A correct link would typically point to the 'new issue' page of the current repository, but since contact_links require absolute URLs, you might consider linking to a general support documentation page or removing this contact link if one doesn't exist.
| ### Releated Issue | ||
| #{{ISSUE_NUMBERs}} |
There was a problem hiding this comment.
This section appears to be malformed. There is a typo in the heading ('Releated' instead of 'Related'), and the placeholder #{{ISSUE_NUMBERs}} is not standard GitHub syntax. The 'Related tickets / issues' section higher up in the template already serves the purpose of linking issues. To avoid confusion, I recommend removing this entire section.
Description
This PR automatically syncs the latest organization templates from the central
.githubrepository to keep this repository aligned with organization-wide standards.Source: Organization
.githubrepositorySync Date: 2025-12-22
Files Updated:
.github/ISSUE_TEMPLATE/bug_report.yaml.github/ISSUE_TEMPLATE/config.yml.github/ISSUE_TEMPLATE/feature_request.yaml.github/ISSUE_TEMPLATE/security_report.yaml.github/ISSUE_TEMPLATE/support_question.yaml.github/PULL_REQUEST_TEMPLATE/pr_form.yml.github/PULL_REQUEST_TEMPLATE/pull_request_template.md.github/workflows/pr_checks.yml.github/workflows/commit-msg-validation.ymlSECURITY.mdThese templates ensure consistency across all organization repositories for:
How to test
Note: If this repository has custom template overrides, verify they still work after merging.
Checklist
.githubrepositoryAdditional Notes
🤖 This PR was automatically generated by the template sync workflow.
What to review:
Need changes? If you need to preserve repository-specific templates, either:
Questions? Contact the organization administrators or comment on this PR.