Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThree documentation files updated: two files receive minor badge label changes from "Enterprise" to "Enterprise Grid," while the workflows documentation undergoes substantial rewording and restructuring, shifting terminology from "work item state transitions" to state management language with reorganized sections for workflow configuration. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 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 docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
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.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
docs/core-concepts/projects/manage-project-members.md (1)
175-183:⚠️ Potential issue | 🔴 CriticalRemove duplicate "How users join projects" section.
This section is identical to lines 138-147. The duplication creates confusion and makes the documentation harder to maintain. Remove one of the instances.
📝 Suggested fix
Delete lines 175-183 entirely, as they duplicate the section that already appears at lines 138-147.
-## How users join projects - -Users can become project members in two different ways, and understanding both helps you manage your project team effectively. - -**Direct project membership** is where you specifically invite users to your project and assign them roles. These members have access only to the projects you've added them to, and you have full control over their permissions. - -**Teamspace-based membership** happens automatically when your project is linked to a [Teamspace](/core-concepts/workspaces/teamspaces). All members of that teamspace automatically receive `Member` access to your project, making it perfect for teams that collaborate across multiple projects. - -Users can have both types of access simultaneously. When this happens, Plane automatically applies whichever role gives them higher permissions. For example, if someone is a `Guest` on your project but joins a linked teamspace, they're automatically upgraded to `Member` access. If they're already an `Admin`, they keep their `Admin` role. -🤖 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` around lines 175 - 183, Remove the duplicate "## How users join projects" block that repeats the explanation of Direct project membership and Teamspace-based membership (the header and the following paragraph describing Direct project membership, Teamspace-based membership, and the upgrade/role-resolution example). Locate the second occurrence of the "## How users join projects" header and delete that entire duplicate section so only the original description remains.docs/workflows-and-approvals/workflows.md (1)
18-31:⚠️ Potential issue | 🟡 MinorRemove or uncomment the embedded demo.
The commented-out iframe code suggests an Arcade demo was planned but not finalized. Either uncomment it if the demo is ready, or remove it entirely to keep the documentation clean.
🧹 Suggested fix
If the demo isn't ready, remove the commented block:
-<!-- -<div style="position: relative; padding-bottom: calc(56.67989417989418% + 41px); height: 0; width: 100%"> - <iframe - src="https://demo.arcade.software/F2dAIS5BLVXcbgWUCQgl?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true" - frameborder="0" - loading="lazy" - webkitallowfullscreen - mozallowfullscreen - allowfullscreen - style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; color-scheme: light" - title="Set up your workspace" - ></iframe> -</div> ---> -🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/workflows-and-approvals/workflows.md` around lines 18 - 31, The commented-out Arcade iframe demo block (the HTML <!-- ... <iframe src="https://demo.arcade.software/..."> ...</iframe> ... -->) should be either removed or uncommented: if the demo is not ready, delete the entire commented block to keep docs clean; if the demo is ready, remove the HTML comment markers so the iframe tag and its wrapper div are active and verify the iframe attributes (src, title, loading, style) are correct and safe for embedding in workflows.md.
🤖 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`:
- Around line 175-183: Remove the duplicate "## How users join projects" block
that repeats the explanation of Direct project membership and Teamspace-based
membership (the header and the following paragraph describing Direct project
membership, Teamspace-based membership, and the upgrade/role-resolution
example). Locate the second occurrence of the "## How users join projects"
header and delete that entire duplicate section so only the original description
remains.
In `@docs/workflows-and-approvals/workflows.md`:
- Around line 18-31: The commented-out Arcade iframe demo block (the HTML <!--
... <iframe src="https://demo.arcade.software/..."> ...</iframe> ... -->) should
be either removed or uncommented: if the demo is not ready, delete the entire
commented block to keep docs clean; if the demo is ready, remove the HTML
comment markers so the iframe tag and its wrapper div are active and verify the
iframe attributes (src, title, loading, style) are correct and safe for
embedding in workflows.md.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ba0cfc2b-a62a-4578-b8d0-d9f9602f19e5
📒 Files selected for processing (3)
docs/authentication/group-sync.mddocs/core-concepts/projects/manage-project-members.mddocs/workflows-and-approvals/workflows.md
sriramveeraghanta
approved these changes
Mar 18, 2026
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.
Summary by CodeRabbit
Documentation