Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughUpdates to product documentation: added instructions for copying branch names and editing/deleting time logs; restructured project membership content and added leave-project/workspace steps; clarified views behavior and introduced a Private views section; small formatting fix to a billing heading. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
sriramveeraghanta
approved these changes
Mar 20, 2026
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
docs/core-concepts/projects/manage-project-members.md (1)
1-1:⚠️ Potential issue | 🔴 CriticalFix formatting issues flagged by oxfmt.
The CI pipeline runs
oxfmt --checkas part of the formatting check. Runpnpm fix:formatto automatically fix formatting issues in all files, oroxfmt --write docs/core-concepts/projects/manage-project-members.mdto fix this file specifically.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/core-concepts/projects/manage-project-members.md` at line 1, Run the formatter to fix Oxfmt formatting errors in the markdown: execute pnpm fix:format to fix all files or run oxfmt --write docs/core-concepts/projects/manage-project-members.md to rewrite this specific file (manage-project-members.md) so it passes the CI oxfmt --check step.docs/workspaces-and-users/billing-and-plans.md (1)
1-1:⚠️ Potential issue | 🔴 CriticalFix trailing whitespace and formatting issues detected by oxfmt.
The file has trailing whitespace on multiple lines (117, 159, 205, 208, 211, and others) along with potential character encoding issues. Run
pnpm fix:formatoroxfmt --write docs/workspaces-and-users/billing-and-plans.mdto automatically resolve these formatting violations.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/workspaces-and-users/billing-and-plans.md` at line 1, Remove trailing whitespace and fix encoding/formatting issues in the billing-and-plans markdown (docs/workspaces-and-users/billing-and-plans.md) by running the repository formatter; run "pnpm fix:format" or "oxfmt --write docs/workspaces-and-users/billing-and-plans.md" to automatically trim trailing spaces and correct character encoding, then re-check the lines mentioned (around lines 117, 159, 205, 208, 211) to confirm no remaining trailing whitespace or stray characters.docs/core-concepts/projects/milestones.md (1)
1-1:⚠️ Potential issue | 🔴 CriticalFix formatting issues flagged by oxfmt.
The CI pipeline reports that
oxfmt check failed: formatting issues found. Runoxfmtwithout the--checkflag to automatically fix formatting issues in this file.#!/bin/bash # Run oxfmt to check and display formatting issues oxfmt --check docs/core-concepts/projects/milestones.md🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/core-concepts/projects/milestones.md` at line 1, The file docs/core-concepts/projects/milestones.md failed oxfmt check; run oxfmt on that file (without --check) to auto-fix formatting, review the changed whitespace/formatting, and commit the updated file so CI passes (e.g., run `oxfmt docs/core-concepts/projects/milestones.md`, verify, then git add/commit).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@docs/core-concepts/projects/manage-project-members.md`:
- Line 1: Run the formatter to fix Oxfmt formatting errors in the markdown:
execute pnpm fix:format to fix all files or run oxfmt --write
docs/core-concepts/projects/manage-project-members.md to rewrite this specific
file (manage-project-members.md) so it passes the CI oxfmt --check step.
In `@docs/core-concepts/projects/milestones.md`:
- Line 1: The file docs/core-concepts/projects/milestones.md failed oxfmt check;
run oxfmt on that file (without --check) to auto-fix formatting, review the
changed whitespace/formatting, and commit the updated file so CI passes (e.g.,
run `oxfmt docs/core-concepts/projects/milestones.md`, verify, then git
add/commit).
In `@docs/workspaces-and-users/billing-and-plans.md`:
- Line 1: Remove trailing whitespace and fix encoding/formatting issues in the
billing-and-plans markdown (docs/workspaces-and-users/billing-and-plans.md) by
running the repository formatter; run "pnpm fix:format" or "oxfmt --write
docs/workspaces-and-users/billing-and-plans.md" to automatically trim trailing
spaces and correct character encoding, then re-check the lines mentioned (around
lines 117, 159, 205, 208, 211) to confirm no remaining trailing whitespace or
stray characters.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 152d7d22-8c72-4ed2-93f0-125c76f0fc7d
📒 Files selected for processing (7)
docs/core-concepts/issues/overview.mddocs/core-concepts/issues/time-tracking.mddocs/core-concepts/projects/manage-project-members.mddocs/core-concepts/projects/milestones.mddocs/core-concepts/views.mddocs/core-concepts/workspaces/members.mddocs/workspaces-and-users/billing-and-plans.md
There was a problem hiding this comment.
🧹 Nitpick comments (1)
docs/core-concepts/workspaces/members.md (1)
131-134: Reformat to match the document's numbered-step pattern.The other procedural sections in this document (inviting members, importing CSV, changing roles, removing members) all use numbered steps. For consistency and improved readability, this section should follow the same format.
📝 Suggested formatting to match document style
## Leave a workspace -If you no longer need access to a workspace, you can leave it yourself. Click the … menu next to your own name in Workspace Settings > Members and select **Leave**. -You'll lose access to the workspace and all its projects immediately. If you need to rejoin later, a Workspace Admin will need to invite you again. +If you no longer need access to a workspace, you can leave it yourself. + +1. Navigate to **Workspace settings > Members**. +2. Click the **…** menu next to your own name. +3. Select **Leave**. +4. Confirm you want to leave. + +You'll lose access to the workspace and all its projects immediately. If you need to rejoin later, a Workspace Admin will need to invite you again.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/core-concepts/workspaces/members.md` around lines 131 - 134, Reformat the "Leave a workspace" section to match the document's numbered-step pattern: convert the current two-paragraph prose under the "## Leave a workspace" heading into a short ordered list of steps (e.g., 1. Open Workspace Settings > Members; 2. Click the … menu next to your name; 3. Select **Leave**), followed by a final numbered note about immediate loss of access and rejoin requiring a Workspace Admin. Ensure the heading text "Leave a workspace" remains unchanged and keep the wording consistent with other procedural sections (use numbered steps and bold UI labels).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/core-concepts/workspaces/members.md`:
- Around line 131-134: Reformat the "Leave a workspace" section to match the
document's numbered-step pattern: convert the current two-paragraph prose under
the "## Leave a workspace" heading into a short ordered list of steps (e.g., 1.
Open Workspace Settings > Members; 2. Click the … menu next to your name; 3.
Select **Leave**), followed by a final numbered note about immediate loss of
access and rejoin requiring a Workspace Admin. Ensure the heading text "Leave a
workspace" remains unchanged and keep the wording consistent with other
procedural sections (use numbered steps and bold UI labels).
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d959eeae-3171-4d1a-8a22-3c18e83ac929
📒 Files selected for processing (5)
docs/core-concepts/issues/overview.mddocs/core-concepts/issues/time-tracking.mddocs/core-concepts/projects/manage-project-members.mddocs/core-concepts/views.mddocs/core-concepts/workspaces/members.md
✅ Files skipped from review due to trivial changes (2)
- docs/core-concepts/issues/overview.md
- docs/core-concepts/issues/time-tracking.md
🚧 Files skipped from review as they are similar to previous changes (2)
- docs/core-concepts/views.md
- docs/core-concepts/projects/manage-project-members.md
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
2 participants
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.
Release Notes
Summary by CodeRabbit