feat(planning): Planning Kanban board UI + graph toggle - #445
Merged
github-actions[bot] merged 1 commit intoJul 3, 2026
Merged
Conversation
Adds the "Planning" sidebar item and the Kanban board it opens, built on the boardStage data layer. Dragging a card between columns persists via notes.setBoardStage (DB metadata only — the note's markdown is untouched). Navigation: - NavigationState gains a 'planning' kind + goToPlanning action + selector - Sidebar "Planning" quick-filter item (KanbanSquare), active-state aware - App.tsx renders <PlanningBoard> in the editor pane for kind==='planning' Board: - PlanningBoard: groups Planning-notebook notes into the 5 Linear-style columns (Backlog/Todo/In Progress/In Review/In Staging); Board|Graph toggle - PlanningColumn: droppable column (native HTML5 DnD, custom MIME) - PlanningCard: draggable card with title, excerpt, tags, and task progress via countMarkdownTasks; click opens the note - Graph mode reuses GraphView with a new filterNotebookId prop that restricts nodes/edges to the Planning notebook Hooks: useNoteMutations.setBoardStage; BoardStage re-exported from preload. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
github-actions
Bot
merged commit Jul 3, 2026
219da96
into
feature/planning-kanban-data
4 of 5 checks passed
This was referenced Jul 3, 2026
tomymaritano
added a commit
that referenced
this pull request
Jul 3, 2026
## Problem The Auto-merge workflow enabled auto-merge on **every** owner PR on `opened`/`synchronize`/`reopened`/`ready_for_review`. Consequences: - PRs to `develop` had auto-merge enabled automatically, so they merged the moment branch protection was satisfied — **before CodeRabbit review was resolved** (the exact CodeRabbit-first violation we keep hitting). - **Stacked PRs targeting an unprotected feature branch merged instantly** (no protection to hold them). This is what collapsed the stacked UI PR (#445) into its base branch before review. ## Fix Owner auto-merge is now **opt-in via the `automerge` label**: - The `automerge-owner` job only runs when the PR carries the `automerge` label, and the workflow now also reacts to the `labeled` event. - Add the label when a PR is genuinely ready to merge; leave it off (or remove it) to hold — no more surprise merges. - Dependabot auto-merge is unchanged. The `automerge` label has been created in the repo. ## Testing Workflow-only change (YAML). Verified the `if:` uses `contains(github.event.pull_request.labels.*.name, 'automerge')` and the `labeled` trigger is present so applying the label enables auto-merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated automated merge behavior to require both a matching PR author and an automation label before merging. * Expanded event handling so labeled pull requests are evaluated for auto-merge eligibility. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The UI half of the Planning Kanban feature. Stacked on #444 (the data layer) — this PR's base is
feature/planning-kanban-dataand will auto-retarget todeveloponce #444 merges. Review #444 first.Adds the "Planning" sidebar item and the Kanban board it opens. Columns are the 5 Linear-style stages; dragging a card persists via
notes.setBoardStage— DB metadata only, the note's markdown is never rewritten ("markdown is sacred").What's included
Navigation
NavigationStategains aplanningkind +goToPlanningaction +selectIsPlanningContextKanbanSquare), active-state awareApp.tsxrenders<PlanningBoard>in the editor pane whennavigation.kind === 'planning'Board (
components/planning/)PlanningBoard— groups Planning-notebook notes into Backlog/Todo/In Progress/In Review/In Staging; Board ↔ Graph togglePlanningColumn— droppable column (native HTML5 DnD, customapplication/x-dripnex-noteMIME — the app's DnD convention, no new dep)PlanningCard— draggable card: title, excerpt, tags, task progress viacountMarkdownTasks; click opens the noteGraphViewvia a new optionalfilterNotebookIdprop that restricts nodes/edges to the Planning notebookHooks:
useNoteMutations.setBoardStage;BoardStagere-exported from preload.Testing
pnpm typecheck(all desktop projects) — greenpnpm test— green;pnpm lint— greenpnpm --filter @dripnex/desktop build— bundles successfullypnpm dev(Planning item → board → drag persists → markdown unchanged → graph toggle)How it connects to the graph
No new graph infra — the existing
GraphView/useGraphData/window.dripnex.linksare reused;filterNotebookIdscopes them to the board's notes (nodes already carrynotebookId).🤖 Generated with Claude Code