Skip to content

docs: add create project with template API endpoint#293

Open
pushya22 wants to merge 2 commits into
masterfrom
docs/create-project-with-template
Open

docs: add create project with template API endpoint#293
pushya22 wants to merge 2 commits into
masterfrom
docs/create-project-with-template

Conversation

@pushya22

@pushya22 pushya22 commented Jun 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Adds documentation for the new POST /api/v1/workspaces/{workspace_slug}/projects/templates/use/ endpoint introduced in plane-ee#7644
  • Follows the existing two-column API doc pattern with path params, body params, scopes, and cURL/Python/JavaScript code examples
  • Added sidebar entry under Projects, after Create Project

Test plan

  • Verify the page renders correctly at /api-reference/project/create-project-with-template
  • Verify sidebar shows "Create Project with Template" after "Create Project" in the Projects section
  • Verify CI (Prettier + VitePress build) passes

🤖 Generated with Claude Code

Summary by CodeRabbit

Documentation

  • Added API reference documentation for creating projects from templates, including HTTP endpoint specifications, required parameters, authentication scopes, and code examples in multiple languages.
  • Updated API navigation menu to reflect the new project template creation guide.

Documents the new POST /api/v1/workspaces/{slug}/projects/templates/use/ endpoint from plane-ee#7644. Adds the page to the Projects sidebar after Create Project.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
developer-docs Ready Ready Preview, Comment Jun 20, 2026 10:46am

Request Review

@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@pushya22, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 53 minutes and 11 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8ae9e25c-b22c-4770-81e2-8e65f18dfdff

📥 Commits

Reviewing files that changed from the base of the PR and between ff7984a and c54516c.

📒 Files selected for processing (1)
  • docs/api-reference/project/overview.md
📝 Walkthrough

Walkthrough

A new API reference page is added documenting the POST endpoint for creating a Plane project from an existing project template. The page covers path/body parameters, required scopes, cURL/Python/JavaScript examples, and a sample 201 response. A matching sidebar entry is registered in the VitePress config.

Changes

Create Project with Template API Reference

Layer / File(s) Summary
API reference page and sidebar registration
docs/.vitepress/config.mts, docs/api-reference/project/create-project-with-template.md
New markdown page with front matter, endpoint description, path and body parameters, required scopes, multi-language code examples (cURL, Python, JavaScript), and a 201 JSON response sample; sidebar entry added under the Project API Reference group linking to /api-reference/project/create-project-with-template.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 A template was waiting, all tidy and neat,
A POST to the endpoint — a project complete!
With name and identifier, lead and a plan,
The docs now explain it as clear as they can.
Hop hop, little rabbit, the sidebar is set! 🌿

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add create project with template API endpoint' directly and accurately describes the main change—adding documentation for a new API endpoint for creating projects with templates, which matches the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/create-project-with-template

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 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/api-reference/project/create-project-with-template.md`:
- Line 21: The markdown document has incorrect heading hierarchy, jumping from
h1 directly to h3 and skipping the h2 level. Change the heading level for the
main section headings "Path Parameters", "Body Parameters", and "Scopes" from h3
(###) to h2 (##) to ensure proper hierarchical progression and comply with
markdown best practices.
- Around line 134-151: The fetch function call with the long URL exceeds the
120-character line width limit. Refactor the const response await fetch
statement by breaking it across multiple lines: place the fetch opening on the
first line, move the URL string to the next line with proper indentation, move
the options object (containing method, headers, and body properties) to the next
line, and place the closing parentheses and semicolon on the final line to
conform to the 120-character line width requirement.
🪄 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: 10177ddb-e2e4-4cc2-bc03-d79401074dc9

📥 Commits

Reviewing files that changed from the base of the PR and between f6749a7 and ff7984a.

📒 Files selected for processing (2)
  • docs/.vitepress/config.mts
  • docs/api-reference/project/create-project-with-template.md


<div class="params-section">

### Path Parameters

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix heading hierarchy: use h2 instead of h3 for main sections.

The document jumps from h1 (# Create project with template) directly to h3 (### Path Parameters), skipping the h2 level. Per markdown best practices and the static analysis flag (MD001), section headings should increment by one level at a time.

Change ### Path Parameters, ### Body Parameters, and ### Scopes to ## Path Parameters, ## Body Parameters, and ## Scopes.

Also applies to: 36-36, 81-81

🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 21-21: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🤖 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/api-reference/project/create-project-with-template.md` at line 21, The
markdown document has incorrect heading hierarchy, jumping from h1 directly to
h3 and skipping the h2 level. Change the heading level for the main section
headings "Path Parameters", "Body Parameters", and "Scopes" from h3 (###) to h2
(##) to ensure proper hierarchical progression and comply with markdown best
practices.

Source: Linters/SAST tools

Comment on lines +134 to +151
```javascript
const response = await fetch("https://api.plane.so/api/v1/workspaces/my-workspace/projects/templates/use/", {
method: "POST",
headers: {
"X-API-Key": "your-api-key",
"Content-Type": "application/json",
},
body: JSON.stringify({
template_id: "7a2d3972-80a5-4ac5-8bb5-03026671826a",
name: "Mobile App Revamp",
identifier: "MAR",
description: "Project created from the Agile Project Setup template",
network: 2,
project_lead: "0d8d8869-3ed1-4fb4-b5c4-ff672888f5e2",
}),
});
const data = await response.json();
```

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Wrap long JavaScript fetch URL to stay within 120-character line width.

Line 135 exceeds the 120-character limit per Prettier guidelines. The fetch URL + opening brace should be split onto multiple lines.

✨ Proposed fix for line wrapping
 <template `#javascript`>

 ```javascript
-const response = await fetch("https://api.plane.so/api/v1/workspaces/my-workspace/projects/templates/use/", {
+const response = await fetch(
+  "https://api.plane.so/api/v1/workspaces/my-workspace/projects/templates/use/",
+  {
   method: "POST",
   headers: {
     "X-API-Key": "your-api-key",
     "Content-Type": "application/json",
   },
   body: JSON.stringify({
     template_id: "7a2d3972-80a5-4ac5-8bb5-03026671826a",
     name: "Mobile App Revamp",
     identifier: "MAR",
     description: "Project created from the Agile Project Setup template",
     network: 2,
     project_lead: "0d8d8869-3ed1-4fb4-b5c4-ff672888f5e2",
   }),
-});
+  },
+);
 const data = await response.json();

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

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/api-reference/project/create-project-with-template.md around lines 134

  • 151, The fetch function call with the long URL exceeds the 120-character line
    width limit. Refactor the const response await fetch statement by breaking it
    across multiple lines: place the fetch opening on the first line, move the URL
    string to the next line with proper indentation, move the options object
    (containing method, headers, and body properties) to the next line, and place
    the closing parentheses and semicolon on the final line to conform to the
    120-character line width requirement.

</details>

<!-- fingerprinting:phantom:triton:mongoose -->

<!-- cr-comment:v1:fecfd93224ce5bd563fd781d -->

_Source: Coding guidelines_

<!-- This is an auto-generated comment by CodeRabbit -->

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants