From ae9a75d31763446bec5a4e4c1b3ab2db4484ae46 Mon Sep 17 00:00:00 2001 From: kirillk Date: Thu, 23 Apr 2026 15:02:59 -0400 Subject: [PATCH] docs: add JetBrains issue filing guidance --- AGENTS.md | 8 ++++++++ packages/kilo-jetbrains/AGENTS.md | 8 ++++++++ 2 files changed, 16 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 3ff6266067..3f80f032c0 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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). diff --git a/packages/kilo-jetbrains/AGENTS.md b/packages/kilo-jetbrains/AGENTS.md index 5a41a647dd..ff44b9af68 100644 --- a/packages/kilo-jetbrains/AGENTS.md +++ b/packages/kilo-jetbrains/AGENTS.md @@ -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` `` entries ↔ module XML descriptors (`kilo.jetbrains.{shared,frontend,backend}.xml`)