feat: add integrations for GitHub

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,156 @@
+name: Bug report
+description: Report a defect in Devlane so we can fix it.
+title: "[BUG] "
+labels: ["bug", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to file a bug report. Please fill in as much detail as you can — it helps us reproduce and fix the problem faster.
+
+        **Do not report security vulnerabilities here.** See [SECURITY.md](../SECURITY.md) for private disclosure.
+
+  - type: checkboxes
+    id: prechecks
+    attributes:
+      label: Pre-submission checks
+      options:
+        - label: I have searched existing issues and this is not a duplicate.
+          required: true
+        - label: I am using the latest `main` or the most recent release.
+          required: true
+        - label: This is not a security vulnerability (those go to SECURITY.md).
+          required: true
+
+  - type: dropdown
+    id: component
+    attributes:
+      label: Affected component
+      options:
+        - API (Go / Gin backend)
+        - UI (React SPA)
+        - Editor (TipTap — description / comments)
+        - Auth (sessions, magic-code, OAuth providers)
+        - Workspaces / Projects / Issues
+        - Modules / Cycles / Views
+        - Activity feed / Notifications
+        - Integrations (GitHub, etc.)
+        - Database / Migrations
+        - Background jobs (RabbitMQ / queue)
+        - File uploads (MinIO)
+        - Email / SMTP
+        - Instance Admin
+        - Docker / Deployment
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      description: How badly does this affect users?
+      options:
+        - Critical — data loss, security exposure, or full outage
+        - High — core flow broken, no workaround
+        - Medium — feature broken with a workaround
+        - Low — cosmetic, edge case, or minor UX issue
+    validations:
+      required: true
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: A clear, concise description of the bug.
+      placeholder: When I drag an issue between board columns, the state badge doesn't update until I refresh.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Minimal, numbered steps. Include sample data or a workspace/project slug if possible.
+      value: |
+        1. Sign in to workspace `…`
+        2. Open project `…`
+        3. …
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Devlane version or commit
+      description: Release tag (e.g. v0.5.1) or git commit SHA from `git rev-parse --short HEAD`.
+      placeholder: v0.5.1 or abc1234
+    validations:
+      required: true
+
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      description: OS, browser (UI bugs), Go version (API bugs), Node version.
+      placeholder: Windows 11, Chrome 132, Go 1.23.4, Node 22.11.0
+    validations:
+      required: true
+
+  - type: dropdown
+    id: deployment
+    attributes:
+      label: Deployment mode
+      options:
+        - Local development (`docker compose up` + `npm run dev` + `go run ./cmd/api`)
+        - Self-hosted production
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: db
+    attributes:
+      label: Database state
+      description: Is your local DB freshly migrated, or could there be schema drift?
+      options:
+        - Fresh — migrations applied cleanly on startup
+        - Existing — could have drift from older migrations
+        - Not applicable
+    validations:
+      required: false
+
+  - type: textarea
+    id: api_logs
+    attributes:
+      label: API logs
+      description: Relevant lines from `go run ./cmd/api` output. Redact session cookies / tokens.
+      render: shell
+
+  - type: textarea
+    id: console_logs
+    attributes:
+      label: Browser console / network output
+      description: Paste console errors or failed request responses. Redact bearer tokens.
+      render: shell
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context
+      description: Screenshots, screen recordings, related issues, or anything else that helps reproduce.

.github/ISSUE_TEMPLATE/chore.yml

@@ -0,0 +1,62 @@
+name: Chore / tech debt
+description: Track maintenance, refactor, dependency upgrade, or cleanup work.
+title: "[CHORE] "
+labels: ["chore", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this for work that doesn't add user-visible features and isn't a bug report — e.g. dependency upgrades, refactors, dead-code removal, CI tuning, or planned tech debt cleanup.
+
+  - type: dropdown
+    id: kind
+    attributes:
+      label: Kind
+      options:
+        - Refactor (no behavior change)
+        - Dependency upgrade
+        - Build / CI / tooling
+        - Test coverage
+        - Performance improvement
+        - Dead code / cleanup
+        - Migration follow-up
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Scope
+      options:
+        - API
+        - UI
+        - Infra / Docker
+        - Repo-wide
+    validations:
+      required: true
+
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Why is this worth doing now? What does ignoring it cost us?
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed approach
+      description: How should this be tackled? Files / modules involved, rough plan.
+
+  - type: textarea
+    id: risk
+    attributes:
+      label: Risk and rollback
+      description: What could regress? How would we revert if it does?
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/Devlaner/devlane/security/advisories/new
+    about: Privately disclose a security issue. Do not file a public bug report.
+  - name: Question or general discussion
+    url: https://github.com/Devlaner/devlane/discussions
+    about: Ask questions, share usage tips, or kick around an idea before opening an issue.

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,57 @@
+name: Documentation
+description: Report missing, incorrect, or unclear documentation.
+title: "[DOCS] "
+labels: ["documentation", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template for problems with `README`, `CLAUDE.md`, in-code comments that mislead, the `planning/` design docs, or any onboarding gap.
+
+  - type: checkboxes
+    id: prechecks
+    attributes:
+      label: Pre-submission checks
+      options:
+        - label: I have searched existing docs issues and this is not a duplicate.
+          required: true
+
+  - type: dropdown
+    id: kind
+    attributes:
+      label: Issue kind
+      options:
+        - Missing — something should be documented but isn't
+        - Incorrect — documented behavior doesn't match reality
+        - Unclear — accurate but hard to follow
+        - Outdated — was correct, isn't anymore
+        - Broken link / formatting
+    validations:
+      required: true
+
+  - type: input
+    id: location
+    attributes:
+      label: Location
+      description: File path, doc URL, or section.
+      placeholder: README.md, planning/backend-architecture.md, code comment in api/internal/router/router.go
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What's wrong or missing?
+    validations:
+      required: true
+
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Suggested wording or structure
+      description: Optional — if you have a concrete suggestion, paste it here.
+
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional context