Repository navigation
docs: auto-sync jetbrains with merged PRs (through 2026-10-25) - #15275
github-actions[bot] wants to merge 4 commits into
Conversation
1f85942 to
1b14643
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| Use **Chat** for the current workspace and **Agents** to manage parallel tasks in isolated git worktrees. **+ Session** starts a conversation; **+ Worktree** opens the worktree creation dialog. | ||
|
|
||
| - **New Worktree** creates a new branch, imports a GitHub pull request with **From PR**, or uses an available local branch with **From Branch**. | ||
| - **New Worktree** creates a new branch, imports a GitHub pull request with **From PR**, or uses an available local branch with **From Branch**. Leave **Fetch latest base branch before creating** enabled (the default) to fetch the selected base branch from its configured remote before the worktree is created, so the new worktree branches from the latest commit instead of a stale local ref. Kilo remembers the choice across projects and IDEs. |
There was a problem hiding this comment.
SUGGESTION: "across projects and IDEs" overstates the persistence scope
KiloPluginSettings stores this preference via PropertiesComponent.getInstance() (packages/kilo-jetbrains/frontend/src/main/kotlin/ai/kilocode/client/plugin/KiloPluginSettings.kt:143), which is application-level: the choice persists across projects and IDE restarts within one JetBrains IDE, but not between different JetBrains IDEs (IntelliJ IDEA and PyCharm keep separate config directories). Consider "Kilo remembers the choice across projects and IDE restarts" to avoid implying it is shared across products.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (1 file)
Fix these issues in Kilo Cloud Reviewed by deepseek-v4.1-flash-1017 · Input: 51.1K · Output: 4.3K · Cached: 539.6K Review guidance: REVIEW.md from base branch |
Automated docs sync — 2026-10-25
This PR keeps kilo.ai/docs in sync with features merged to Kilo-Org/cloud and Kilo-Org/kilocode. Every change below links to the merged PR it documents.
2026-10-24T07:03:19.791Z→2026-10-25T07:03:39.767ZSurface:
jetbrainsother(the explicit other prefixes are listed under other.docs). The cloud surfaces are derived the same way from the Kilo-Org/cloud layout: cloud-mobile = apps/mobile/, cloud-web = apps/web/, cloud-extension = apps/extension/, and cloud-agent = the cloud-agent packages under packages/ (packages/cloud-agent-sdk/ + packages/cloud-agent-profile/). A cloud source names its repository while a bare string still means this repository. The pages under packages/kilo-docs/pages/collaborate/ document the cloud web app (app.kilo.ai: teams dashboard, billing, SSO, adoption dashboard), so they route to cloud-web. No page under packages/kilo-docs/pages/ documents the browser side-panel extension yet, so cloud-extension lists no docs prefix..github/docs-sync/surfaces.jsoncli,vscode,jetbrains,gateway,web,cloud-mobile,cloud-web,cloud-extension,cloud-agent,otherpackages/kilo-jetbrains/packages/kilo-docs/pages/code-with-ai/platforms/jetbrains.mdother:packages/kilo-docs/pages/community/,packages/kilo-docs/pages/contributing/,packages/kilo-docs/LEARNINGS.md,docs/jetbrainsare ranked from git history overpackages/kilo-jetbrains/(a commit 180 days old counts half as much, half-life 180 days). Bots (author type "Bot" or a login matching /[bot]$/i) and people without admin, write, or maintain permission are excluded.Changes
Pending — will retry
None.
Considered, no docs change needed
(bot) Generated by the docs-sync workflow. Humans review and merge; while this PR stays open, the next daily run appends new changes here. Branch:
docs/auto-sync-2026-10-25.