Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
74 changes: 74 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
name: "🐞 Bug report"
description: "Report a reproducible bug so we can investigate and fix it quickly."
title: "[BUG] "
labels: ["bug", "triage"]
assignees: []
body:
- type: markdown
attributes:
value: |
Thanks for filing a bug — please fill in the details below. Provide as much context as you can to help us reproduce and fix the issue.
- type: input
id: summary
attributes:
label: Short summary
description: A one-line summary of the bug.
placeholder: e.g. "Crash when opening settings with locale=fr"
validations:
required: true
- type: textarea
id: steps
attributes:
label: Steps to reproduce
description: Step-by-step list to reproduce the bug.
placeholder: |
1. Go to ...
2. Click ...
3. See error
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected behavior
description: What you expected to happen.
placeholder: "Settings should open without crashing."
validations:
required: true
- type: textarea
id: actual
attributes:
label: Actual behavior
description: What actually happened.
placeholder: "App crashes with stacktrace ..."
validations:
required: true
- type: textarea
id: logs
attributes:
label: Logs / error output / stack trace (if any)
description: Attach or paste logs. Use backticks for code blocks.
placeholder: "Paste logs, stack traces, or attach files."
- type: checkboxes
id: attachments
attributes:
label: Attachments
description: Add screenshots, recordings, or example files if helpful.
options:
- label: I have attached necessary screenshots / repro assets
- type: dropdown
id: severity
attributes:
label: Severity
options:
- "blocker — blocks development or release"
- "major — feature broken or severe bug"
- "minor — small bug, workaround exists"
- "cosmetic — UI/typo"
validations:
required: true
- type: textarea
id: notes
attributes:
label: Additional notes
description: Anything else the maintainers should know.
9 changes: 9 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Organization-level Issue Form config
blank_issues_enabled: false
contact_links:
- name: Security policy (private)
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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

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.

about: "Use the 'Support / Question' template for product/help requests."
53 changes: 53 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
name: "💡 Feature request"
description: "Suggest an improvement or new feature — include the problem it solves."
title: "[FEATURE] "
labels: ["enhancement", "triage", "proposal"]
assignees: []
body:
- type: markdown
attributes:
value: |
Thanks for suggesting a feature! Please describe the use-case and why it's valuable.
- type: input
id: title_short
attributes:
label: Short summary
placeholder: "Add CSV export to reporting UI"
validations:
required: true
- type: textarea
id: problem
attributes:
label: Problem statement
description: What problem does this feature solve? Who benefits?
validations:
required: true
- type: textarea
id: proposal
attributes:
label: Proposed solution / design
description: How would you like this to work? Include examples, mockups or API changes.
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: Any alternatives or workarounds you tried.
- type: dropdown
id: priority
attributes:
label: Business priority
options:
- "P0 — critical"
- "P1 — important"
- "P2 — nice-to-have"
- "P3 — low priority"
validations:
required: true
- type: input
id: contacts
attributes:
label: Contacts
description: Who requested this, who will be impacted, or what triggered this request?
placeholder: "team@example.com/in email from user@example.com"
43 changes: 43 additions & 0 deletions .github/ISSUE_TEMPLATE/security_report.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
name: "🔐 Security vulnerability report"
description: "Report a potential security vulnerability. Do NOT include sensitive secrets or PII in this issue — use the private disclosure channel described below."
title: "[SECURITY] "
labels: ["security", "triage", "private"]
assignees: []
body:
- type: markdown
attributes:
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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

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.

* If this is non-sensitive proof-of-concept information safe for public view, fill the form below.
- type: input
id: summary
attributes:
label: Short summary
placeholder: "SQL injection in /api/endpoint"
validations:
required: true
- type: textarea
id: impact
attributes:
label: Impact
description: What could an attacker do? Data exposure, RCE, privilege escalation, etc.
validations:
required: true
- type: textarea
id: poc
attributes:
label: Proof-of-concept (non-sensitive)
description: Steps or code to reproduce (do NOT include secrets).
- type: input
id: disclosure_contact
attributes:
label: Contact email (for private follow-up)
validations:
required: true
- type: textarea
id: notes
attributes:
label: Additional notes
description: Anything else maintainers should know.
39 changes: 39 additions & 0 deletions .github/ISSUE_TEMPLATE/support_question.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
name: "❓ Support / Question"
description: "Ask for help with using the project, configuration, or setup issues."
title: "[SUPPORT] "
labels: ["support", "triage"]
assignees: []
body:
- type: markdown
attributes:
value: |
Use this template for usage questions, configuration help, or troubleshooting that is not a bug.
- type: input
id: summary
attributes:
label: Short summary
placeholder: "How to configure X with Y?"
validations:
required: true
- type: textarea
id: context
attributes:
label: Context / background
description: Where are you running this? What versions/config did you try?
placeholder: "I am using docker-compose on Ubuntu 22.04..."
validations:
required: true
- type: textarea
id: attempt
attributes:
label: What you tried
placeholder: "I tried ... but got ..."
- type: textarea
id: expected
attributes:
label: What you expected to happen
- type: input
id: contact
attributes:
label: Preferred contact (email / handle)
description: If maintainers need follow-up, how should we reach you?
155 changes: 155 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/pr_form.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,155 @@
name: "📦 Pull Request"
description: "Submit a PR with structured details for review."
title: "[PR] "
labels: []
body:
- type: markdown
attributes:
value: |
# 📦 Pull Request
Thanks for contributing! Please fill in all required fields to ensure smooth review.

- type: input
id: summary
attributes:
label: Short summary (one line)
description: "e.g., feat(auth): add SSO login"
placeholder: "Short descriptive title"
validations:
required: true

- type: textarea
id: description
attributes:
label: Description
description: "What does this PR do? Why is it needed?"
placeholder: "Provide context for the change..."
validations:
required: true

- type: dropdown
id: type_of_change
attributes:
label: Type of change
options:
- Bug fix
- New feature
- Breaking change
- Chore / refactor / documentation
validations:
required: true

- type: textarea
id: related_issues
attributes:
label: Related tickets / issues
description: "List related issue numbers, e.g., Closes #123"
placeholder: "Closes #123"
validations:
required: false

- type: textarea
id: changes
attributes:
label: Proposed changes
description: "List key changes included in this PR."
placeholder: |
- Added ...
- Updated ...
- Removed ...
validations:
required: true

- type: textarea
id: test_instructions
attributes:
label: How to test / QA
description: "Provide clear steps for reviewers/testers."
placeholder: |
1. Checkout branch...
2. Run tests...
3. Verify behavior...
validations:
required: true

- type: checkboxes
id: checklist
attributes:
label: Checklist (required)
description: Ensure your PR meets these requirements.
options:
- label: Tests added/updated and passing locally
- label: Documentation updated (if applicable)
- label: Linting and formatting completed
- label: PR title follows repo conventions (e.g., conventional commits)
- label: No sensitive data or secrets are included
validations:
required: true

- type: textarea
id: rollout
attributes:
label: Rollout plan & backwards compatibility
description: "List deployment steps, flags, compatibility notes."
placeholder: "This change is backward compatible because..."
validations:
required: false

- type: textarea
id: migrations
attributes:
label: Database migrations (if any)
description: "Describe any migrations and whether they are safe/additive."
placeholder: |
- Migration script: /sql/migrations/xxx.sql
- Up: ...
- Down: ...
validations:
required: false

- type: textarea
id: security
attributes:
label: Security considerations
description: "Does this PR affect auth, secrets, PII, or permissions?"
placeholder: |
- No sensitive data
- Touches auth: added validation...
validations:
required: false

- type: textarea
id: performance
attributes:
label: Performance considerations
description: "Any impact on speed, memory, or scaling?"
placeholder: "No measurable performance impact."
validations:
required: false

- type: textarea
id: screenshots
attributes:
label: Screenshots / recordings
description: "If UI changed, include visuals."
placeholder: "Attach before/after screenshots..."
validations:
required: false

- type: input
id: changelog
attributes:
label: Changelog entry
description: "Short entry for release notes."
placeholder: "Added support for X in API Y"
validations:
required: false

- type: input
id: reviewers
attributes:
label: Suggested reviewers
description: "Tag team members or @teams as needed."
placeholder: "@your-team"
validations:
required: false
Loading