Update GitHub issue and PR templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,57 @@
+---
+name: Bug Report
+about: Report a bug
+labels: bug
+---
+
+## Bug Report
+
+### Orchestrator version
+
+<!-- Output of `orchestrator --version` -->
+
+### Backend
+
+<!-- MySQL or SQLite? -->
+
+### Configuration
+
+<!-- Paste your orchestrator.conf.json below (sanitized — remove passwords and sensitive hostnames) -->
+
+```json
+
+```
+
+### Topology
+
+<!-- Paste the output of `orchestrator-client -c topology -alias my-cluster` -->
+
+```
+
+```
+
+### Steps to reproduce
+
+1.
+2.
+3.
+
+### Expected behavior
+
+<!-- What did you expect to happen? -->
+
+### Actual behavior
+
+<!-- What happened instead? -->
+
+### Logs
+
+<!-- Please include relevant orchestrator logs. Use `--debug --stack` for maximum verbosity. -->
+
+```
+
+```
+
+### Additional context
+
+<!-- Any other information that might be helpful (OS, MySQL version, raft/non-raft mode, etc.) -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature Request
+about: Suggest a new feature
+labels: enhancement
+---
+
+## Feature Request
+
+### Problem description / use case
+
+<!-- What problem are you trying to solve? Why is this feature needed? -->
+
+### Proposed solution
+
+<!-- How do you envision this feature working? -->
+
+### Alternatives considered
+
+<!-- Have you considered any alternative solutions or workarounds? -->
+
+### Additional context
+
+<!-- Any other information, mockups, or references that might be helpful. -->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,11 @@
+---
+name: Question
+about: Ask a question about orchestrator
+labels: question
+---
+
+## Question
+
+<!-- Please check the documentation first: https://github.com/proxysql/orchestrator/tree/master/docs -->
+
+<!-- Ask your question below. Include as much context as possible (version, setup, what you've tried). -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,31 +1,17 @@
-<!--
-## A Pull Request should be associated with an Issue.
-
-> We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
-> If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
-> and potentially we'll be able to point development in a particular direction.
-Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR
--->
-
-Related issue: https://github.com/openark/orchestrator/issues/0123456789
+## Pull Request
 
+Related issue: https://github.com/proxysql/orchestrator/issues/
 
 ### Description
 
-This PR [briefly explain what is does]
-
-<!--
-Please make sure that:
+This PR [briefly explain what it does]
 
-- [ ] contributed code is using same conventions as original code
+### Checklist
 
-Please make sure the PR passes CI tests. For your information, CI tests the following:
+Please review the [contribution guidelines](CONTRIBUTING.md) before submitting.
 
-- code is formatted via `gofmt` (please avoid `goimports`)
-- code passes compilation
-- code passes unit tests
-- code passes integration tests with MySQL backend
-- code passes integration tests with SQLite backend
-- There are no orphaned docs/ pages (there's some link in the docs to point to any page)
-- upgrade from previous version (`master` branch) is successful
- -->
+- [ ] Code formatted with `gofmt` (please avoid `goimports`)
+- [ ] Tests added/updated
+- [ ] CI passes (unit, integration, system tests)
+- [ ] DCO sign-off included (`git commit -s`)
+- [ ] Related issue linked above