RomanNum3ral
/
honcho
mirror of https://github.com/plastic-labs/honcho.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore: slim bug/quality forms and add integration template 

Drop high-friction required fields from bug and quality issue forms.
Add an integration-request form (app stores, plugins, frameworks) labeled
integration, and point contributing docs at it.
This commit is contained in:
Aakash Kattelu 2026-08-18 09:43:06 -04:00
parent cc44963924
commit 088cb16a76
7 changed files with 77 additions and 127 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
.github/ISSUE_TEMPLATE/1-bug-report.yml vendored
View File

@ -24,46 +24,6 @@ body:
validations:
required: true
- type: dropdown
id: component
attributes:
label: Component
description: Where does the bug show up?
options:
- API / HTTP routes
- Deriver / queue / message processing
- Dreamer / consolidation
- Dialectic / chat endpoint
- Summarizer / session context
- Auth / JWT / API keys
- Embeddings / vector search
- Python SDK
- TypeScript SDK
- CLI
- Managed offering (dashboard, billing, hosted infra)
- Docs
- Other
validations:
required: true
- type: input
id: server_version
attributes:
label: Honcho server version
description: Image tag, PyPI/git revision, or release (e.g. `v2.4.1`, `main@abc1234`, Docker digest).
placeholder: e.g. v2.4.1
validations:
required: true
- type: input
id: sdk_version
attributes:
label: SDK / client version (if applicable)
description: Python `honcho-ai` or TypeScript `@honcho-ai/sdk` version, or "n/a".
placeholder: e.g. honcho-ai 1.2.0 / n/a
validations:
required: false
- type: textarea
id: description
attributes:
@ -86,41 +46,6 @@ body:
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected behavior
description: What you expected to happen.
validations:
required: true
- type: textarea
id: actual
attributes:
label: Actual behavior
description: What actually happened (error messages, status codes, incorrect data).
validations:
required: true
- type: dropdown
id: regression
attributes:
label: Is this a regression?
options:
- "No"
- "Yes — it worked in an earlier version"
- Unsure
validations:
required: true
- type: input
id: last_good_version
attributes:
label: Last known good version (if regression)
placeholder: e.g. v2.3.0
validations:
required: false
- type: textarea
id: logs
attributes:
@ -134,6 +59,6 @@ body:
id: context
attributes:
label: Additional context
description: Config knobs (provider, deriver/dream settings), deployment notes, related issues/PRs.
description: Versions, config knobs, deployment notes, related issues/PRs.
validations:
required: false

48
.github/ISSUE_TEMPLATE/2-quality-report.yml vendored
View File

@ -23,31 +23,6 @@ body:
validations:
required: true
- type: dropdown
id: surface
attributes:
label: Which surface looks wrong?
description: Pick the closest match; add detail below if several apply.
options:
- Conclusions (extracted memory)
- Dialectic / chat answers
- Peer representation / peer card
- Session context / summaries
- Search (messages or conclusions)
- Dreamer consolidation / reasoning
- Other
validations:
required: true
- type: input
id: server_version
attributes:
label: Honcho server version
description: Image tag, revision, or release.
placeholder: e.g. v2.4.1
validations:
required: true
- type: textarea
id: description
attributes:
@ -57,14 +32,6 @@ body:
validations:
required: true
- type: textarea
id: expected
attributes:
label: What should have happened instead?
description: Ideal conclusions, answer, or representation behavior.
validations:
required: true
- type: textarea
id: repro
attributes:
@ -81,21 +48,6 @@ body:
validations:
required: true
- type: dropdown
id: reasoning_level
attributes:
label: Dialectic reasoning level (if chat-related)
options:
- n/a — not chat-related
- minimal
- low
- medium
- high
- max
- Unsure / default
validations:
required: true
- type: textarea
id: config
attributes:

70
.github/ISSUE_TEMPLATE/4-integration-request.yml vendored Normal file
View File

@ -0,0 +1,70 @@
name: Integration request
description: Add Honcho to an app store, agent framework, plugin marketplace, or other third-party surface — or improve an existing integration.
title: "[Integration] "
labels: ["integration"]
body:
- type: markdown
attributes:
value: |
Use this when you want Honcho available in (or better supported by) an external product surface — app stores, agent frameworks, plugin marketplaces, IDE extensions, MCP clients, etc.
For core API/SDK product features that are not about a third-party surface, use the **Feature request** template instead.
- type: dropdown
id: request_kind
attributes:
label: What kind of request is this?
options:
- New integration / listing (Honcho is not there yet)
- Improve an existing integration
- Official plugin / extension
- Marketplace or app-store listing
- Docs / guide for integrating with a specific tool
- Other
validations:
required: true
- type: input
id: target
attributes:
label: Target product or platform
description: Name of the app, framework, marketplace, or tool.
placeholder: e.g. Claude Code, Cursor, CrewAI, OpenClaw, VS Code Marketplace…
validations:
required: true
- type: input
id: target_url
attributes:
label: Link (if any)
description: Docs, marketplace page, repo, or product URL.
placeholder: https://…
validations:
required: false
- type: textarea
id: why
attributes:
label: Why does this matter?
description: Who would use it, and what does the integration unlock?
validations:
required: true
- type: textarea
id: shape
attributes:
label: What should the integration look like?
description: >
e.g. one-click install, MCP server listing, native memory backend,
SDK recipe, plugin with slash commands, env-var setup, etc.
Link to prior art or a sketch if you have one.
validations:
required: false
- type: textarea
id: context
attributes:
label: Additional context
description: Related issues, community demand, constraints, offers to help build it.
validations:
required: false

0
.github/ISSUE_TEMPLATE/4-docs-bug.md → .github/ISSUE_TEMPLATE/5-docs-bug.md vendored
View File

3
CONTRIBUTING.md
View File

@ -196,7 +196,7 @@ We welcome various types of contributions:
When reporting bugs or requesting features:
1. Check if the issue already exists
2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, or feature)
2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, or integration)
3. Provide clear reproduction steps for bugs
4. Include relevant environment information (managed vs self-hosted, server version, SDK)
5. Be specific about expected vs actual behavior
@ -208,6 +208,7 @@ When reporting bugs or requesting features:
- **Bug reports** - GitHub issues → Bug report template
- **Memory / recall quality** - GitHub issues → Memory / recall quality template
- **Feature requests** - GitHub issues → Feature request template
- **Integrations / plugins / app-store listings** - GitHub issues → Integration request template
- **Security issues** - Report **privately** only — see [`SECURITY.md`](./SECURITY.md) (GitHub Private Vulnerability Reporting or email). Do not open a public issue.
## License

3
docs/v2/contributing/guidelines.mdx
View File

@ -153,7 +153,7 @@ We welcome various types of contributions:
When reporting bugs or requesting features:
1. Check if the issue already exists
2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, or feature)
2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, or integration)
3. Provide clear reproduction steps for bugs
4. Include relevant environment information (managed vs self-hosted, server version, SDK)
5. Be specific about expected vs actual behavior
@ -165,6 +165,7 @@ When reporting bugs or requesting features:
- **Bug reports** - GitHub issues → Bug report template
- **Memory / recall quality** - GitHub issues → Memory / recall quality template
- **Feature requests** - GitHub issues → Feature request template
- **Integrations / plugins / app-store listings** - GitHub issues → Integration request template
- **Security issues** - Report **privately** only — see [`SECURITY.md`](https://github.com/plastic-labs/honcho/blob/main/SECURITY.md) (GitHub Private Vulnerability Reporting or email). Do not open a public issue.
## License

3
docs/v3/contributing/guidelines.mdx
View File

@ -153,7 +153,7 @@ We welcome various types of contributions:
When reporting bugs or requesting features:
1. Check if the issue already exists
2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, or feature)
2. Use the appropriate [issue template](https://github.com/plastic-labs/honcho/issues/new/choose) (bug, memory/recall quality, feature, or integration)
3. Provide clear reproduction steps for bugs
4. Include relevant environment information (managed vs self-hosted, server version, SDK)
5. Be specific about expected vs actual behavior
@ -165,6 +165,7 @@ When reporting bugs or requesting features:
- **Bug reports** - GitHub issues → Bug report template
- **Memory / recall quality** - GitHub issues → Memory / recall quality template
- **Feature requests** - GitHub issues → Feature request template
- **Integrations / plugins / app-store listings** - GitHub issues → Integration request template
- **Security issues** - Report **privately** only — see [`SECURITY.md`](https://github.com/plastic-labs/honcho/blob/main/SECURITY.md) (GitHub Private Vulnerability Reporting or email). Do not open a public issue.
## License