Add Desktop app#473
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. 📝 WalkthroughWalkthroughAdds a complete Plane desktop app documentation page covering setup, connectivity, usage, updates, and platform behavior, and links it from the Devices sidebar alongside the Mobile page. ChangesDesktop documentation
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/devices/desktop.md`:
- Line 6: Update the page heading in desktop.md to match the existing Desktop
sidebar label from the docs configuration, preserving the heading’s meaning and
changing only the capitalization/text needed for an exact match.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b1fa1d45-56fb-4b47-b948-13b55398bb86
📒 Files selected for processing (2)
docs/.vitepress/config.tsdocs/devices/desktop.md
| - **macOS** | ||
| - **Linux** | ||
|
|
||
| To connect to a self-managed deployment, the instance must be on **Plane Commercial v3.0.0 or later**. Earlier versions do not support the desktop app. |
There was a problem hiding this comment.
We should also note that they need to be using desktop app version 3.0.0 or later.
| - **Open a new tab** with the **+** button at the end of the tab bar, or **New tab** (Cmd/Ctrl+T). | ||
| - **Close a tab** with the **X** on the tab, or **Close tab** (Cmd/Ctrl+W). You cannot close the last remaining tab in a window. | ||
| - **Reorder tabs** by dragging them along the tab bar. | ||
| - **Go back and forward** using the arrows to the left of the tabs. |
There was a problem hiding this comment.
It’s not there yet; we have Ctrl+Tab or Ctrl+Shift+Tab for tab switching.
Doc follow-ups (from review) + OAuth desktop callbacks (shipped in product)Building on the inline notes on this PR, here’s a short summary of what would be good to add or clarify in Suggested doc additions / corrections
What we did in product (for cross-link)God Mode now surfaces those desktop callback URIs next to Web / Mobile / Admin, mirroring the mobile pattern—so self-managed admins can copy-paste without digging through API routes.
Once that ships, this docs PR can reference it (and optionally the God Mode Authentication screens) so the OAuth self-managed steps stay accurate for desktop, not only mobile. Happy to expand any of these into full draft copy if useful. |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/devices/desktop.md (1)
18-22: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winInclude Windows in the supported-systems list.
The introduction says the app supports macOS, Windows, and Linux, but this requirements list omits Windows. Add it so Windows users are not incorrectly told the app is unsupported.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/devices/desktop.md` around lines 18 - 22, Update the supported-systems list in the desktop app introduction to include Windows alongside macOS and Linux, matching the documented platform support.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/devices/desktop.md`:
- Line 88: Update the tab shortcut bullet in the desktop documentation to
describe switching to the next/previous tab, replacing the misleading “Go back
and forward” label while preserving the existing Ctrl+Tab and Ctrl+Shift+Tab
shortcuts.
---
Outside diff comments:
In `@docs/devices/desktop.md`:
- Around line 18-22: Update the supported-systems list in the desktop app
introduction to include Windows alongside macOS and Linux, matching the
documented platform support.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| - **Open a new tab** with the **+** button at the end of the tab bar, or **New tab** (Cmd/Ctrl+T). | ||
| - **Close a tab** with the **X** on the tab, or **Close tab** (Cmd/Ctrl+W). You cannot close the last remaining tab in a window. | ||
| - **Reorder tabs** by dragging them along the tab bar. | ||
| - **Go back and forward** Ctrl+Tab / Ctrl+Shift+Tab for next/previous tab. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Describe tab switching, not history navigation.
Ctrl+Tab and Ctrl+Shift+Tab switch between tabs, but “Go back and forward” suggests browser history navigation and conflicts with the table below. Rename this bullet to “Switch to the next/previous tab.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/devices/desktop.md` at line 88, Update the tab shortcut bullet in the
desktop documentation to describe switching to the next/previous tab, replacing
the misleading “Go back and forward” label while preserving the existing
Ctrl+Tab and Ctrl+Shift+Tab shortcuts.
2 participants
Description
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References
Summary by CodeRabbit