opensource/kilocode
3
0
Fork 0
mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-08-28 19:11:03 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: add JetBrains issue filing guidance

Browse Source
This commit is contained in:
kirillk
2026-04-23 15:02:59 -04:00
parent 0a39e11a04
commit ae9a75d317
2 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+8
View File
@@ -181,6 +181,14 @@ Changeset descriptions appear directly in release notes and are read by end user
PR descriptions should be 2-3 lines covering **what** changed and **why**. Focus on intent and context a reviewer can't get from the diff — skip file-by-file inventories, test result summaries, and anything obvious from the code itself.
## GitHub Issues
- When creating a GitHub issue for the JetBrains plugin, use the repo's existing issue templates in `.github/ISSUE_TEMPLATE/`. Pick the matching template (`Bug report`, `Feature Request`, or `Question`) instead of opening a blank issue.
- Do not add JetBrains-specific title prefixes such as `[JetBrains]`, `[Jetbrains]`, `[JB]`, or similar. Use a plain, descriptive title.
- Always add JetBrains plugin issues to the GitHub project `Jetbrains Plugin`: https://github.com/orgs/Kilo-Org/projects/39
- When using `gh`, prefer `gh issue create --template "..." --project "Jetbrains Plugin"`.
- If project assignment fails because `gh` is missing the required scope, run `gh auth refresh -s project` and retry.
## Fork Merge Process
Kilo CLI is a fork of [opencode](https://github.com/anomalyco/opencode).
packages/kilo-jetbrains/AGENTS.md
+8
View File
@@ -68,6 +68,14 @@
- **Via Turbo**: `bun turbo build --filter=@kilocode/kilo-jetbrains` from repo root.
- **Run in sandbox**: `./gradlew runIde` — launches sandboxed IntelliJ with the plugin. Does NOT build CLI binaries.
## GitHub Issues
- When creating a GitHub issue for the JetBrains plugin, use the repo's existing issue templates in `.github/ISSUE_TEMPLATE/`. Pick the matching template (`Bug report`, `Feature Request`, or `Question`) instead of opening a blank issue.
- Do not add JetBrains-specific title prefixes such as `[JetBrains]`, `[Jetbrains]`, `[JB]`, or similar. Use a plain, descriptive title.
- Always add JetBrains plugin issues to the GitHub project `Jetbrains Plugin`: https://github.com/orgs/Kilo-Org/projects/39
- When using `gh`, prefer `gh issue create --template "..." --project "Jetbrains Plugin"`.
- If project assignment fails because `gh` is missing the required scope, run `gh auth refresh -s project` and retry.
## Files That Must Change Together
- `plugin.xml` `<content>` entries ↔ module XML descriptors (`kilo.jetbrains.{shared,frontend,backend}.xml`)