Skip to content

Commit ea80855

Browse files
authored
chore: sync organization templates (#1)
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.
1 parent 4c187f7 commit ea80855

10 files changed

Lines changed: 860 additions & 0 deletions

File tree

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
name: "🐞 Bug report"
2+
description: "Report a reproducible bug so we can investigate and fix it quickly."
3+
title: "[BUG] "
4+
labels: ["bug", "triage"]
5+
assignees: []
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
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.
11+
- type: input
12+
id: summary
13+
attributes:
14+
label: Short summary
15+
description: A one-line summary of the bug.
16+
placeholder: e.g. "Crash when opening settings with locale=fr"
17+
validations:
18+
required: true
19+
- type: textarea
20+
id: steps
21+
attributes:
22+
label: Steps to reproduce
23+
description: Step-by-step list to reproduce the bug.
24+
placeholder: |
25+
1. Go to ...
26+
2. Click ...
27+
3. See error
28+
validations:
29+
required: true
30+
- type: textarea
31+
id: expected
32+
attributes:
33+
label: Expected behavior
34+
description: What you expected to happen.
35+
placeholder: "Settings should open without crashing."
36+
validations:
37+
required: true
38+
- type: textarea
39+
id: actual
40+
attributes:
41+
label: Actual behavior
42+
description: What actually happened.
43+
placeholder: "App crashes with stacktrace ..."
44+
validations:
45+
required: true
46+
- type: textarea
47+
id: logs
48+
attributes:
49+
label: Logs / error output / stack trace (if any)
50+
description: Attach or paste logs. Use backticks for code blocks.
51+
placeholder: "Paste logs, stack traces, or attach files."
52+
- type: checkboxes
53+
id: attachments
54+
attributes:
55+
label: Attachments
56+
description: Add screenshots, recordings, or example files if helpful.
57+
options:
58+
- label: I have attached necessary screenshots / repro assets
59+
- type: dropdown
60+
id: severity
61+
attributes:
62+
label: Severity
63+
options:
64+
- "blocker — blocks development or release"
65+
- "major — feature broken or severe bug"
66+
- "minor — small bug, workaround exists"
67+
- "cosmetic — UI/typo"
68+
validations:
69+
required: true
70+
- type: textarea
71+
id: notes
72+
attributes:
73+
label: Additional notes
74+
description: Anything else the maintainers should know.

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Organization-level Issue Form config
2+
blank_issues_enabled: false
3+
contact_links:
4+
- name: Security policy (private)
5+
url: https://github.com/RKInnovate/.github/blob/main/SECURITY.md
6+
about: "Report security vulnerabilities (private channel). Use this for sensitive security issues only."
7+
- name: General support
8+
url: https://github.com/RKInnovate/.github/ISSUE_TEMPLATE#support--questions
9+
about: "Use the 'Support / Question' template for product/help requests."
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
name: "💡 Feature request"
2+
description: "Suggest an improvement or new feature — include the problem it solves."
3+
title: "[FEATURE] "
4+
labels: ["enhancement", "triage", "proposal"]
5+
assignees: []
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Thanks for suggesting a feature! Please describe the use-case and why it's valuable.
11+
- type: input
12+
id: title_short
13+
attributes:
14+
label: Short summary
15+
placeholder: "Add CSV export to reporting UI"
16+
validations:
17+
required: true
18+
- type: textarea
19+
id: problem
20+
attributes:
21+
label: Problem statement
22+
description: What problem does this feature solve? Who benefits?
23+
validations:
24+
required: true
25+
- type: textarea
26+
id: proposal
27+
attributes:
28+
label: Proposed solution / design
29+
description: How would you like this to work? Include examples, mockups or API changes.
30+
validations:
31+
required: true
32+
- type: textarea
33+
id: alternatives
34+
attributes:
35+
label: Alternatives considered
36+
description: Any alternatives or workarounds you tried.
37+
- type: dropdown
38+
id: priority
39+
attributes:
40+
label: Business priority
41+
options:
42+
- "P0 — critical"
43+
- "P1 — important"
44+
- "P2 — nice-to-have"
45+
- "P3 — low priority"
46+
validations:
47+
required: true
48+
- type: input
49+
id: contacts
50+
attributes:
51+
label: Contacts
52+
description: Who requested this, who will be impacted, or what triggered this request?
53+
placeholder: "team@example.com/in email from user@example.com"
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
name: "🔐 Security vulnerability report"
2+
description: "Report a potential security vulnerability. Do NOT include sensitive secrets or PII in this issue — use the private disclosure channel described below."
3+
title: "[SECURITY] "
4+
labels: ["security", "triage", "private"]
5+
assignees: []
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
**Security disclosure instructions**
11+
* Do NOT post exploits, PII, credentials, or sensitive attachments in a public issue.
12+
* If you have sensitive details, email: security@ORG-DOMAIN (or use our private disclosure process) — see SECURITY.md.
13+
* If this is non-sensitive proof-of-concept information safe for public view, fill the form below.
14+
- type: input
15+
id: summary
16+
attributes:
17+
label: Short summary
18+
placeholder: "SQL injection in /api/endpoint"
19+
validations:
20+
required: true
21+
- type: textarea
22+
id: impact
23+
attributes:
24+
label: Impact
25+
description: What could an attacker do? Data exposure, RCE, privilege escalation, etc.
26+
validations:
27+
required: true
28+
- type: textarea
29+
id: poc
30+
attributes:
31+
label: Proof-of-concept (non-sensitive)
32+
description: Steps or code to reproduce (do NOT include secrets).
33+
- type: input
34+
id: disclosure_contact
35+
attributes:
36+
label: Contact email (for private follow-up)
37+
validations:
38+
required: true
39+
- type: textarea
40+
id: notes
41+
attributes:
42+
label: Additional notes
43+
description: Anything else maintainers should know.
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
name: "❓ Support / Question"
2+
description: "Ask for help with using the project, configuration, or setup issues."
3+
title: "[SUPPORT] "
4+
labels: ["support", "triage"]
5+
assignees: []
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Use this template for usage questions, configuration help, or troubleshooting that is not a bug.
11+
- type: input
12+
id: summary
13+
attributes:
14+
label: Short summary
15+
placeholder: "How to configure X with Y?"
16+
validations:
17+
required: true
18+
- type: textarea
19+
id: context
20+
attributes:
21+
label: Context / background
22+
description: Where are you running this? What versions/config did you try?
23+
placeholder: "I am using docker-compose on Ubuntu 22.04..."
24+
validations:
25+
required: true
26+
- type: textarea
27+
id: attempt
28+
attributes:
29+
label: What you tried
30+
placeholder: "I tried ... but got ..."
31+
- type: textarea
32+
id: expected
33+
attributes:
34+
label: What you expected to happen
35+
- type: input
36+
id: contact
37+
attributes:
38+
label: Preferred contact (email / handle)
39+
description: If maintainers need follow-up, how should we reach you?
Lines changed: 155 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,155 @@
1+
name: "📦 Pull Request"
2+
description: "Submit a PR with structured details for review."
3+
title: "[PR] "
4+
labels: []
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
# 📦 Pull Request
10+
Thanks for contributing! Please fill in all required fields to ensure smooth review.
11+
12+
- type: input
13+
id: summary
14+
attributes:
15+
label: Short summary (one line)
16+
description: "e.g., feat(auth): add SSO login"
17+
placeholder: "Short descriptive title"
18+
validations:
19+
required: true
20+
21+
- type: textarea
22+
id: description
23+
attributes:
24+
label: Description
25+
description: "What does this PR do? Why is it needed?"
26+
placeholder: "Provide context for the change..."
27+
validations:
28+
required: true
29+
30+
- type: dropdown
31+
id: type_of_change
32+
attributes:
33+
label: Type of change
34+
options:
35+
- Bug fix
36+
- New feature
37+
- Breaking change
38+
- Chore / refactor / documentation
39+
validations:
40+
required: true
41+
42+
- type: textarea
43+
id: related_issues
44+
attributes:
45+
label: Related tickets / issues
46+
description: "List related issue numbers, e.g., Closes #123"
47+
placeholder: "Closes #123"
48+
validations:
49+
required: false
50+
51+
- type: textarea
52+
id: changes
53+
attributes:
54+
label: Proposed changes
55+
description: "List key changes included in this PR."
56+
placeholder: |
57+
- Added ...
58+
- Updated ...
59+
- Removed ...
60+
validations:
61+
required: true
62+
63+
- type: textarea
64+
id: test_instructions
65+
attributes:
66+
label: How to test / QA
67+
description: "Provide clear steps for reviewers/testers."
68+
placeholder: |
69+
1. Checkout branch...
70+
2. Run tests...
71+
3. Verify behavior...
72+
validations:
73+
required: true
74+
75+
- type: checkboxes
76+
id: checklist
77+
attributes:
78+
label: Checklist (required)
79+
description: Ensure your PR meets these requirements.
80+
options:
81+
- label: Tests added/updated and passing locally
82+
- label: Documentation updated (if applicable)
83+
- label: Linting and formatting completed
84+
- label: PR title follows repo conventions (e.g., conventional commits)
85+
- label: No sensitive data or secrets are included
86+
validations:
87+
required: true
88+
89+
- type: textarea
90+
id: rollout
91+
attributes:
92+
label: Rollout plan & backwards compatibility
93+
description: "List deployment steps, flags, compatibility notes."
94+
placeholder: "This change is backward compatible because..."
95+
validations:
96+
required: false
97+
98+
- type: textarea
99+
id: migrations
100+
attributes:
101+
label: Database migrations (if any)
102+
description: "Describe any migrations and whether they are safe/additive."
103+
placeholder: |
104+
- Migration script: /sql/migrations/xxx.sql
105+
- Up: ...
106+
- Down: ...
107+
validations:
108+
required: false
109+
110+
- type: textarea
111+
id: security
112+
attributes:
113+
label: Security considerations
114+
description: "Does this PR affect auth, secrets, PII, or permissions?"
115+
placeholder: |
116+
- No sensitive data
117+
- Touches auth: added validation...
118+
validations:
119+
required: false
120+
121+
- type: textarea
122+
id: performance
123+
attributes:
124+
label: Performance considerations
125+
description: "Any impact on speed, memory, or scaling?"
126+
placeholder: "No measurable performance impact."
127+
validations:
128+
required: false
129+
130+
- type: textarea
131+
id: screenshots
132+
attributes:
133+
label: Screenshots / recordings
134+
description: "If UI changed, include visuals."
135+
placeholder: "Attach before/after screenshots..."
136+
validations:
137+
required: false
138+
139+
- type: input
140+
id: changelog
141+
attributes:
142+
label: Changelog entry
143+
description: "Short entry for release notes."
144+
placeholder: "Added support for X in API Y"
145+
validations:
146+
required: false
147+
148+
- type: input
149+
id: reviewers
150+
attributes:
151+
label: Suggested reviewers
152+
description: "Tag team members or @teams as needed."
153+
placeholder: "@your-team"
154+
validations:
155+
required: false

0 commit comments

Comments
 (0)