Asana clickup linear Connecters#454
Closed
Pranesh-Raghu wants to merge 1 commit intoscalekit-inc:mainfrom
Closed
Conversation
Pranesh-Raghu
requested review from
amitash1912,
ravibits and
saif-at-scalekit
as code owners
Contributor
WalkthroughAdds comprehensive Setup and Usage guides to three agent connector documentation files (Asana, ClickUp, Linear), including OAuth configuration steps, credential management instructions, and code examples in Python and Node.js with tab-based formatting. No functional code changes present. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
🚥 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)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
src/content/docs/reference/agent-connectors/clickup.mdx (2)
74-74: 🧹 Nitpick | 🔵 TrivialRemove unused
Codeimport.Same as the other connector files — the
Codecomponent is imported but not used.♻️ Proposed fix
-import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } from '@astrojs/starlight/components' +import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside } from '@astrojs/starlight/components'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/reference/agent-connectors/clickup.mdx` at line 74, Remove the unused Code component from the import list in the module where Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code are imported (the import statement that currently includes Code); update the import to only include the actually used symbols (e.g., remove the "Code" identifier) so the file no longer imports an unused component.
82-82:⚠️ Potential issue | 🟡 MinorFix incorrect CDN domain for logo image.
The image URL uses
cdn.scalekit.combut should usecdn.scalekit.cloudper the established pattern for agent connector documentation. This will cause the logo to fail to load.🐛 Proposed fix
- <img src="https://cdn.scalekit.com/sk-connect/assets/provider-icons/clickup.svg" width="64" height="64" alt="ClickUp logo" /> + <img src="https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/clickup.svg" width="64" height="64" alt="ClickUp logo" />Based on learnings: "For any agent connector documentation files located in src/content/docs/reference/agent-connectors/, prefer using CDN URLs for connector logos (https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/)".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/reference/agent-connectors/clickup.mdx` at line 82, The logo image src in the <img> tag currently points to https://cdn.scalekit.com/sk-connect/assets/provider-icons/clickup.svg; update that URL to use the correct CDN domain https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/clickup.svg so the ClickUp logo loads properly (edit the src attribute in the <img> element in the clickup.mdx file).src/content/docs/reference/agent-connectors/asana.mdx (1)
74-74: 🧹 Nitpick | 🔵 TrivialRemove unused
Codeimport.The
Codecomponent is imported but never used in this file. Per repository guidelines, only import components that are actually used to reduce bundle size.♻️ Proposed fix
-import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } from '@astrojs/starlight/components' +import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside } from '@astrojs/starlight/components'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/reference/agent-connectors/asana.mdx` at line 74, The file imports the Code component but never uses it; remove the unused import to follow repo guidelines and reduce bundle size by deleting "Code" from the import statement that currently reads "import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } from '@astrojs/starlight/components'"; ensure the remaining imports (Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside) remain and run a quick lint/build to verify no other references to Code exist.src/content/docs/reference/agent-connectors/linear.mdx (1)
74-74: 🧹 Nitpick | 🔵 TrivialRemove unused
Codeimport.Same as asana.mdx — the
Codecomponent is imported but not used.♻️ Proposed fix
-import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } from '@astrojs/starlight/components' +import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside } from '@astrojs/starlight/components'🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/reference/agent-connectors/linear.mdx` at line 74, Remove the unused named import "Code" from the import statement that currently reads "import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code } from '@astrojs/starlight/components'"; update that import to only include the components actually used (Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside) to eliminate the unused symbol.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/reference/agent-connectors/asana.mdx`:
- Around line 183-218: The Python example lacks a code-block title and does not
show error handling for the proxy request; update the fenced code block to
include a title attribute (e.g., ```python title="connect_asana.py"```) and wrap
the call to actions.request (the request to "/api/1.0/users/me") in a try/except
that prints a clear error message on exception (e.g., catch Exception as e and
print a descriptive "Request failed" message), leaving the existing calls to
scalekit.client.ScalekitClient, actions.get_authorization_link, connection_name,
and identifier unchanged.
- Around line 145-219: The docs currently only show an active Python TabItem and
a commented-out Node.js example; per guidelines include all four language tabs
(Node.js, Python, Go, Java) once SDKs support Agent Auth. Update the <Tabs
syncKey="tech-stack"> block to uncomment and enable the Node.js TabItem (the
example using ScalekitClient, connectedAccounts.getMagicLinkForConnectedAccount
and actions.request) and add equivalent Go and Java TabItem examples (showing
how to obtain the authorization link and call actions.request/request equivalent
using the SDKs' client/ScalekitClient and actions methods), while leaving the
working Python TabItem intact; if SDKs aren’t yet available, keep a short TODO
comment in each missing TabItem referencing the connector name/identifier
pattern so reviewers know to add real samples later.
In `@src/content/docs/reference/agent-connectors/clickup.mdx`:
- Around line 181-216: Add a title attribute to the Python code block (e.g.,
```python title="connect_clickup.py"```) and wrap the actions.request call in a
try/except to handle API errors; specifically, update the example around
actions.request (and its surrounding print) to catch Exception as e and print a
clear error message (e.g., "Request failed: {e}") so failures like expired
tokens or permission errors are surfaced to the user.
In `@src/content/docs/reference/agent-connectors/linear.mdx`:
- Around line 178-214: Add a title attribute to the Python code block (e.g.,
title="connect_linear.py") and wrap the API call to actions.request in a
try/except to catch and log errors; update the TabItem's Python example around
the actions.request call (where actions.request is invoked with connection_name,
identifier, path="/graphql", method="POST", body=...) to print the result on
success and print or log the exception on failure so the example shows basic
error handling.
---
Outside diff comments:
In `@src/content/docs/reference/agent-connectors/asana.mdx`:
- Line 74: The file imports the Code component but never uses it; remove the
unused import to follow repo guidelines and reduce bundle size by deleting
"Code" from the import statement that currently reads "import { Card, CardGrid,
Tabs, TabItem, Badge, Steps, Aside, Code } from
'@astrojs/starlight/components'"; ensure the remaining imports (Card, CardGrid,
Tabs, TabItem, Badge, Steps, Aside) remain and run a quick lint/build to verify
no other references to Code exist.
In `@src/content/docs/reference/agent-connectors/clickup.mdx`:
- Line 74: Remove the unused Code component from the import list in the module
where Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside, Code are imported (the
import statement that currently includes Code); update the import to only
include the actually used symbols (e.g., remove the "Code" identifier) so the
file no longer imports an unused component.
- Line 82: The logo image src in the <img> tag currently points to
https://cdn.scalekit.com/sk-connect/assets/provider-icons/clickup.svg; update
that URL to use the correct CDN domain
https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/clickup.svg so the
ClickUp logo loads properly (edit the src attribute in the <img> element in the
clickup.mdx file).
In `@src/content/docs/reference/agent-connectors/linear.mdx`:
- Line 74: Remove the unused named import "Code" from the import statement that
currently reads "import { Card, CardGrid, Tabs, TabItem, Badge, Steps, Aside,
Code } from '@astrojs/starlight/components'"; update that import to only include
the components actually used (Card, CardGrid, Tabs, TabItem, Badge, Steps,
Aside) to eliminate the unused symbol.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (3)
src/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📜 Review details
🧰 Additional context used
📓 Path-based instructions (3)
**/*.mdx
📄 CodeRabbit inference engine (.cursorrules)
**/*.mdx: Use clear, descriptive titles that explain the purpose of the document
Include comprehensive descriptions in frontmatter metadata
Organize content with logical heading hierarchy (H2, H3, H4)
Use tableOfContents property in frontmatter when content has multiple sections
Set appropriate sidebar labels for navigation in frontmatter
Use direct instruction writing style with phrases like 'This guide shows you how to...' and 'Create an authorization URL to...'
Use second person perspective ('your application', 'you receive', 'you must') in documentation
Keep sentences concise, aiming for under 25 words per sentence
Explain the 'why' in documentation with phrases like 'This prevents CSRF attacks by...' or 'Use this to validate that...'
Use action verbs in section headings: 'Store session tokens securely', 'Validate the state parameter', 'Exchange authorization code for tokens'
Use present tense for descriptions: 'Scalekit handles the complex authentication flow', 'The SDK provides methods to refresh tokens'
Use future tense for results: 'This will redirect users to...', 'You'll receive a JWT containing...', 'Scalekit returns an authorization code'
Use transition phrases between sections: 'After the user authenticates...', 'Once the state is validated...', 'Let's take a look at how to...'
Write 1-3 opening paragraphs that explain what users will accomplish, provide context about when/why, preview key concepts, and use direct instructional language
Begin introduction sections with a clear statement of what the guide covers and explain the problem being solved
Use collapsible sections in introduction for sequence diagrams, video demonstrations, data models, and JSON examples with appropriate icons
Use numbered format within Steps component:1. ## Titlewith all step content indented with exactly 3 spaces
Use action-oriented headings in step-by-step guides within Steps components
Include code examples in all 4 languages (Node.js, Python, Go, Java) within Steps co...
Files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
⚙️ CodeRabbit configuration file
**/*.mdx: You are reviewing Scalekit developer documentation written in MDX
(Astro + Starlight framework). Apply ALL of the following checks:Frontmatter
titleMUST be ≤ 60 characters and clearly state what the page does.descriptionMUST be ≤ 160 characters, action-oriented, unique per page.sidebar.labelMUST be present and ≤ 30 characters.sidebar.orderMUST be set on every page that lives inside a section
with siblings, to enforce the journey order in sidebar.config.ts.- Flag any missing
prev/nextlinks on pages that are clearly
part of a sequential flow (e.g., quickstart → implement-login →
complete-login → manage-session → logout).Voice & Style (CLAUDE.md standards)
- Voice: confident, direct, collaborative, instructional.
- Person: second person only ("you", "your application"). Reject "we",
"our", "the developer", "the user".- Tense: present tense for descriptions; imperative mood for instructions.
- Flag weasel words: "simply", "just", "easy", "straightforward",
"obviously", "of course", "note that".- Flag passive voice constructions where active voice is clearer.
- Headings must be sentence case, not Title Case (except proper nouns).
- No heading should end with a colon or period.
Content structure
- How-to guides MUST contain numbered
<Steps>(Starlight component).- Concept pages MUST NOT contain numbered steps — concepts explain, not instruct.
- API reference pages MUST list parameters in a table with Name / Type /
Required / Description columns.- Every page MUST end with a clear "what's next" signal — either a
next:frontmatter link, a<LinkCard>, or an explicit paragraph
pointing the reader forward in the sidebar journey.Code examples
- ALL code examples that show SDK usage MUST include all four language
tabs: Node.js, Python, Go, Java — using<Tabs syncKey="tech-stack">.- SDK variable names are STRICTLY:
scalekit(Node.js),
scalekit_client(Python),scalekitClient(Go), ...
Files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
**/*.{yml,yaml,md,mdx}
📄 CodeRabbit inference engine (.cursor/rules/browsecentral-labels.mdc)
**/*.{yml,yaml,md,mdx}: BrowseCentral labels should be maximum 3-5 words - keep concise but add context when needed
BrowseCentral labels should be action-oriented - start with verbs when possible
BrowseCentral labels should be specific and clear - add context when simple labels are ambiguous
BrowseCentral labels should be outcome-focused - describe what users accomplish and the context
BrowseCentral labels should use 'Action + Object' pattern (e.g., 'Invite users', 'Restrict sign-up', 'Set up SCIM')
BrowseCentral labels should use feature names (e.g., 'Enterprise SSO', 'Passwordless quickstart')
BrowseCentral labels should describe task completion (e.g., 'Run migrations', 'Migrate auth', 'Merge identities')
BrowseCentral labels should include specific context when needed (e.g., 'Configure Scalekit MCP server', 'Validate incoming API requests')
BrowseCentral labels should use integration context when applicable (e.g., 'Build MCP auth with your existing auth system')
BrowseCentral labels should avoid instructional prefixes: 'How to', 'Guide to', 'Implement', 'Configure', 'Learn', 'Understand'
BrowseCentral labels should avoid verbose phrases: 'Step-by-step guide', 'Complete tutorial', 'Detailed documentation'
BrowseCentral labels should avoid weak verbs: 'Enable', 'Allow', 'Provide', 'Support'
Files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
**/*.{md,mdx}
📄 CodeRabbit inference engine (.cursor/rules/deno-docs-style.mdc)
**/*.{md,mdx}: Use sentence case for all titles and headings in MD/MDX documentation
Keep page titles short and descriptive (3–7 words when possible) in MD/MDX documentation
Use outcome-focused headings that describe results, not categories (e.g., 'Run a script' not 'Scripts')
Avoid gerunds in headings when an imperative works - prefer 'Configure proxies' over 'Configuring proxies'
Keep sidebar labels concise (1–3 words), use sentence case, and focus on outcomes or objects
Use sentence case in sidebar labels without punctuation
Set frontmatter title in sentence case with a clear outcome; description in one sentence (≤160 chars); sidebar.label as shorter form of title; enable tableOfContents on longer pages
Start documentation pages with a one-paragraph overview explaining what the page covers and when to use it
Present the primary use case (80% path) first in documentation, with edge cases later
Use numbered steps for task-focused sections in documentation, with each step beginning with a verb
Break up long documentation sections with subheadings every 3–6 paragraphs
Use asides for important notes, tips, cautions, and references in documentation
Provide runnable, minimal code examples that work as-is in documentation
Prefer CLI-first examples and show file layout when helpful in documentation
Label code blocks with titles for context (e.g., 'Terminal', 'main.ts') in documentation
Keep code block annotations brief and purposeful - annotate only what matters
Use consistent variable and file names across a documentation page
Use descriptive link text in documentation (e.g., 'See permission flags' not 'click here')
Prefer relative links for internal documentation pages and include anchors for section references
Reference APIs consistently using backticks for code, file names, CLI flags, and endpoints
Use backticks for code, file names, CLI flags, and endpoints in documentation
Use lists for options and features in documentation; tables only when comparisons are cleare...
Files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
🧠 Learnings (21)
📓 Common learnings
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:55.583Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, the parameter tables (showing tool properties) are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Any table format corrections must be made in the generation script, not by manually editing the generated MDX files. The script should be updated to output the required "Name | Type | Required | Description" four-column table format per coding guidelines.
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:46.903Z
Learning: For auto-generated agent connector documentation pages in src/content/docs/reference/agent-connectors/, the "what's next" signal requirement (next: frontmatter link, <LinkCard>, or concluding paragraph) does not apply. These are reference pages generated by scripts/sync-agent-connectors.js and serve as lookup resources rather than sequential guides.
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:37.207Z
Learning: In src/content/docs/reference/agent-connectors/** MDX files, tool headings (e.g., `googlesheets_create_spreadsheet`, `googlesheets_get_values`) intentionally use H2 (##) instead of H3 to ensure they appear in the table of contents for easier navigation. This is a deliberate UX choice for agent connector reference pages and should not be flagged as a hierarchy issue.
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:27.672Z
Learning: For MDX files under src/content/docs/reference/agent-connectors/, do not enforce the 160-character description limit. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may have longer descriptions from the source data.
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:82-82
Timestamp: 2026-02-26T07:21:12.772Z
Learning: For agent connector documentation files under src/content/docs/reference/agent-connectors/, prefer CDN URLs (https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/) for connector logo images rather than storing them locally in src/assets/docs/. This differs from the general guideline to use local assets.
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/native-app.mdx:72-179
Timestamp: 2026-02-02T05:55:51.251Z
Learning: In the `src/content/docs/authenticate/fsa/multiapp/` directory, the multi-app authentication documentation (native-app.mdx, single-page-app.mdx, web-app.mdx, overview.mdx) currently uses conceptual shell/curl examples instead of multi-language SDK code examples because the Scalekit SDKs have not yet been built/updated for multi-app functionality. Once the SDKs are ready, these files should be updated to include all 4 languages (Node.js, Python, Go, Java) using `<Tabs syncKey="tech-stack">`.
📚 Learning: 2026-02-26T07:21:32.951Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:89-131
Timestamp: 2026-02-26T07:21:32.951Z
Learning: For agent-connectors reference MDX files, use H2 headings (##) for tool sections (e.g., googlesheets_create_spreadsheet, googlesheets_get_values) so they appear in the table of contents. This is a deliberate UX choice and should not be flagged as a hierarchy issue.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-26T07:22:49.128Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:95-141
Timestamp: 2026-02-26T07:22:49.128Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, parameter tables are auto-generated from JSON API responses by scripts/sync-agent-connectors.js. Do not manually edit the generated MDX files. Update scripts/sync-agent-connectors.js to output a four-column table with headers Name | Type | Required | Description for all parameter tables, ensuring consistency with the coding guidelines. This pattern should apply to all MDX files in that directory.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-26T07:20:42.107Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlemeet.mdx:1-87
Timestamp: 2026-02-26T07:20:42.107Z
Learning: In src/content/docs/reference/agent-connectors/**, these auto-generated agent connector reference pages (e.g., googlemeet.mdx) are lookup resources. Do not require or enforce the 'what's next' signal (next link, LinkCard, or concluding paragraph) for these pages; treat them as non-sequential references produced by scripts (scripts/sync-agent-connectors.js).
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-26T07:23:24.179Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/microsoftword.mdx:3-3
Timestamp: 2026-02-26T07:23:24.179Z
Learning: Do not enforce the 160-character description limit for MDX files under src/content/docs/reference/agent-connectors/. These files are auto-generated from API payloads via scripts/sync-agent-connectors.js and may contain longer descriptions sourced from the data.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-26T07:18:41.518Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: scripts/sync-agent-connectors.js:0-0
Timestamp: 2026-02-26T07:18:41.518Z
Learning: For MDX files under src/content/docs/reference/agent-connectors, the sidebar.label frontmatter is not required because navigation is auto-generated from this directory via the central sidebar config. Do not rely on or modify sidebar.label in these files; ensure ordering and grouping are defined in the shared sidebar configuration.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-26T07:21:09.133Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 448
File: src/content/docs/reference/agent-connectors/googlesheets.mdx:82-82
Timestamp: 2026-02-26T07:21:09.133Z
Learning: For any agent connector documentation files located in src/content/docs/reference/agent-connectors/, prefer using CDN URLs for connector logos (https://cdn.scalekit.cloud/sk-connect/assets/provider-icons/) instead of inlining or storing images in local assets (e.g., src/assets/docs/). This should override the general guideline to use local assets for this specific docs section. Apply this pattern to all mdx files in that directory; use the CDN-hosted logo URLs in image elements or logo references.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-01-13T12:46:55.260Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include use case comments explaining scenarios in code examples: '// Use case: Provision a workspace after a sales-assisted onboarding'
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdx
📚 Learning: 2026-02-25T18:40:05.360Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-02-25T18:40:05.360Z
Learning: Applies to src/content/docs/guides/integrations/**/*.mdx : Integration guides located in `src/content/docs/guides/integrations/` MUST be kept synchronized with their index pages at `sso-integrations/index.mdx`, `social-connections/index.mdx`, and `scim-integrations/index.mdx`
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdx
📚 Learning: 2026-02-02T05:55:51.251Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/native-app.mdx:72-179
Timestamp: 2026-02-02T05:55:51.251Z
Learning: In the `src/content/docs/authenticate/fsa/multiapp/` directory, the multi-app authentication documentation (native-app.mdx, single-page-app.mdx, web-app.mdx, overview.mdx) currently uses conceptual shell/curl examples instead of multi-language SDK code examples because the Scalekit SDKs have not yet been built/updated for multi-app functionality. Once the SDKs are ready, these files should be updated to include all 4 languages (Node.js, Python, Go, Java) using `<Tabs syncKey="tech-stack">`.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdx
📚 Learning: 2026-01-30T18:18:50.883Z
Learnt from: AkshayParihar33
Repo: scalekit-inc/developer-docs PR: 415
File: src/content/docs/authenticate/fsa/multiapp/manage-apps.mdx:31-49
Timestamp: 2026-01-30T18:18:50.883Z
Learning: In all Scalekit documentation files (MDX), treat the terms 'Applications', 'Single Page Application (SPA)', 'Native Application', and 'Web Application' as proper nouns and preserve their capitalization in headings and body text. Ensure these terms remain capitalized even when used in sentence case or within prose.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-04T12:47:16.544Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 412
File: src/content/docs/dev-kit/tools/scalekit-dryrun.mdx:1-23
Timestamp: 2026-02-04T12:47:16.544Z
Learning: In scalekit-inc/developer-docs, the MDX frontmatter field order is required only when the sidebar configuration points to a directory (for auto-generation). If the sidebar.config.ts references a specific file path, the order field is not required. Apply this check to all MDX files under src/content/docs: if a file contributes to an auto-generated sidebar (directory path), ensure order is present; if it’s linked to a concrete file, order can be omitted. Use sidebar.config.ts to determine whether a given MDX file falls under directory-based vs file-specific sidebar references.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-25T08:57:12.201Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/quickstart.mdx:2-10
Timestamp: 2026-02-25T08:57:12.201Z
Learning: In Scalekit developer-docs (Astro Starlight), do not auto-suggest adding tableOfContents in frontmatter unless the user explicitly overrides the default behavior. The default enables tableOfContents with minHeadingLevel 2 and maxHeadingLevel 3. Only set tableOfContents when you want to customize heading levels or disable it entirely; otherwise omit it for other docs.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-25T13:04:27.491Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:9-17
Timestamp: 2026-02-25T13:04:27.491Z
Learning: Allow page-level CSS overrides in MDX frontmatter (head: style) for readability and engagement, even if it customizes typography beyond defaults. This applies to per-page UX decisions, including heading sizes and style tweaks, but keep overrides purposeful, accessible, and within the repository's design guidelines. Use these overrides sparingly and document the rationale for maintainability.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-25T03:34:41.147Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/start-agent-auth-coding-agents.mdx:31-31
Timestamp: 2026-02-25T03:34:41.147Z
Learning: In MDX files, import { Code } from 'astrojs/starlight/components' only if the MDX content actually uses the <Code> component. If the file uses only fenced code blocks (```), the import is not required. Apply this guideline to all MDX files (e.g., src/content/docs/**/*.mdx) to avoid unnecessary imports and reduce bundle size.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-25T18:41:00.639Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 446
File: src/content/docs/authenticate/m2m/api-auth-quickstart.mdx:78-78
Timestamp: 2026-02-25T18:41:00.639Z
Learning: Preserve full URLs inside code comments in MDX code blocks (bash/python/js) when the URLs are part of copyable examples. Do not flag these in code examples. Use relative paths in prose and hyperlinks within MDX; only enforce relative paths for markdown prose links, not for URLs inside code comments.
Applied to files:
src/content/docs/reference/agent-connectors/clickup.mdxsrc/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-25T13:33:04.619Z
Learnt from: saif-at-scalekit
Repo: scalekit-inc/developer-docs PR: 444
File: src/content/docs/agent-auth/quickstart.mdx:47-47
Timestamp: 2026-02-25T13:33:04.619Z
Learning: In Agent Auth documentation (src/content/docs/agent-auth/**/*.mdx), the Node.js SDK installation must use scalekit-sdk/node2.2.0-beta.1 because Agent Auth features are currently only available in the beta version, not in the latest stable release. Do not flag this as an issue or suggest upgrading to stable versions.
Applied to files:
src/content/docs/reference/agent-connectors/asana.mdxsrc/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-01-13T12:46:55.260Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Use future tense for results: 'This will redirect users to...', 'You'll receive a JWT containing...', 'Scalekit returns an authorization code'
Applied to files:
src/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-01-13T12:48:11.566Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursor/rules/documentation-guide.mdc:0-0
Timestamp: 2026-01-13T12:48:11.566Z
Learning: Applies to **/*.mdx : Use Steps component for sequential instructions in MDX documentation
Applied to files:
src/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-01-13T12:46:55.260Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: .cursorrules:0-0
Timestamp: 2026-01-13T12:46:55.260Z
Learning: Applies to **/*.mdx : Include configuration comments in code examples: '// Get the signing secret from Scalekit dashboard > Interceptors tab'
Applied to files:
src/content/docs/reference/agent-connectors/linear.mdx
📚 Learning: 2026-02-25T18:40:05.360Z
Learnt from: CR
Repo: scalekit-inc/developer-docs PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-02-25T18:40:05.360Z
Learning: Applies to **/*.{md,mdx} : Use Node.js variable name `scalekit` in all SDK examples
Applied to files:
src/content/docs/reference/agent-connectors/linear.mdx
Comment on lines
+145
to
+219
| <Tabs syncKey="tech-stack"> | ||
| {/* Node.js - commented out, uncomment when ready | ||
| <TabItem label="Node.js"> | ||
| ```typescript | ||
| import { ScalekitClient } from '@scalekit-sdk/node'; | ||
| import 'dotenv/config'; | ||
|
|
||
| const connectionName = 'asana'; // get your connection name from connection configurations | ||
| const identifier = 'user_123'; // your unique user identifier | ||
|
|
||
| // Get your credentials from app.scalekit.com → Developers → Settings → API Credentials | ||
| const scalekit = new ScalekitClient( | ||
| process.env.SCALEKIT_ENV_URL, | ||
| process.env.SCALEKIT_CLIENT_ID, | ||
| process.env.SCALEKIT_CLIENT_SECRET | ||
| ); | ||
| const { connectedAccounts, actions } = scalekit; | ||
|
|
||
| // Authenticate the user | ||
| const { link } = await connectedAccounts.getMagicLinkForConnectedAccount({ | ||
| connector: connectionName, | ||
| identifier, | ||
| }); | ||
| console.log('🔗 Authorize Asana:', link); | ||
| process.stdout.write('Press Enter after authorizing...'); | ||
| await new Promise(r => process.stdin.once('data', r)); | ||
|
|
||
| // Make a request via Scalekit proxy | ||
| const result = await actions.request({ | ||
| connectionName, | ||
| identifier, | ||
| path: '/api/1.0/users/me', | ||
| method: 'GET', | ||
| }); | ||
| console.log(result); | ||
| ``` | ||
| </TabItem> | ||
| */} | ||
| <TabItem label="Python"> | ||
| ```python | ||
| import scalekit.client, os | ||
| from dotenv import load_dotenv | ||
| load_dotenv() | ||
|
|
||
| connection_name = "asana" # get your connection name from connection configurations | ||
| identifier = "user_123" # your unique user identifier | ||
|
|
||
| # Get your credentials from app.scalekit.com → Developers → Settings → API Credentials | ||
| scalekit_client = scalekit.client.ScalekitClient( | ||
| client_id=os.getenv("SCALEKIT_CLIENT_ID"), | ||
| client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"), | ||
| env_url=os.getenv("SCALEKIT_ENV_URL"), | ||
| ) | ||
| actions = scalekit_client.actions | ||
|
|
||
| # Authenticate the user | ||
| link_response = actions.get_authorization_link( | ||
| connection_name=connection_name, | ||
| identifier=identifier | ||
| ) | ||
| # present this link to your user for authorization, or click it yourself for testing | ||
| print("🔗 Authorize Asana:", link_response.link) | ||
| input("Press Enter after authorizing...") | ||
|
|
||
| # Make a request via Scalekit proxy | ||
| result = actions.request( | ||
| connection_name=connection_name, | ||
| identifier=identifier, | ||
| path="/api/1.0/users/me", | ||
| method="GET" | ||
| ) | ||
| print(result) | ||
| ``` | ||
| </TabItem> | ||
| </Tabs> |
Contributor
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial
Track: Add Go and Java examples when SDKs are ready.
The coding guidelines require all 4 language tabs (Node.js, Python, Go, Java) for SDK examples. Currently only Python is active, with Node.js commented out. When the Agent Auth SDK features are available in stable releases, uncomment Node.js and add Go/Java examples.
Would you like me to open an issue to track adding the remaining language examples once the SDKs support Agent Auth features?
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/content/docs/reference/agent-connectors/asana.mdx` around lines 145 -
219, The docs currently only show an active Python TabItem and a commented-out
Node.js example; per guidelines include all four language tabs (Node.js, Python,
Go, Java) once SDKs support Agent Auth. Update the <Tabs syncKey="tech-stack">
block to uncomment and enable the Node.js TabItem (the example using
ScalekitClient, connectedAccounts.getMagicLinkForConnectedAccount and
actions.request) and add equivalent Go and Java TabItem examples (showing how to
obtain the authorization link and call actions.request/request equivalent using
the SDKs' client/ScalekitClient and actions methods), while leaving the working
Python TabItem intact; if SDKs aren’t yet available, keep a short TODO comment
in each missing TabItem referencing the connector name/identifier pattern so
reviewers know to add real samples later.
Comment on lines
+183
to
+218
| <TabItem label="Python"> | ||
| ```python | ||
| import scalekit.client, os | ||
| from dotenv import load_dotenv | ||
| load_dotenv() | ||
|
|
||
| connection_name = "asana" # get your connection name from connection configurations | ||
| identifier = "user_123" # your unique user identifier | ||
|
|
||
| # Get your credentials from app.scalekit.com → Developers → Settings → API Credentials | ||
| scalekit_client = scalekit.client.ScalekitClient( | ||
| client_id=os.getenv("SCALEKIT_CLIENT_ID"), | ||
| client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"), | ||
| env_url=os.getenv("SCALEKIT_ENV_URL"), | ||
| ) | ||
| actions = scalekit_client.actions | ||
|
|
||
| # Authenticate the user | ||
| link_response = actions.get_authorization_link( | ||
| connection_name=connection_name, | ||
| identifier=identifier | ||
| ) | ||
| # present this link to your user for authorization, or click it yourself for testing | ||
| print("🔗 Authorize Asana:", link_response.link) | ||
| input("Press Enter after authorizing...") | ||
|
|
||
| # Make a request via Scalekit proxy | ||
| result = actions.request( | ||
| connection_name=connection_name, | ||
| identifier=identifier, | ||
| path="/api/1.0/users/me", | ||
| method="GET" | ||
| ) | ||
| print(result) | ||
| ``` | ||
| </TabItem> |
Contributor
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial
Add title attribute and error handling to code example.
Per coding guidelines, code blocks should include a title attribute showing the file context, and examples should demonstrate both success and error paths.
♻️ Suggested improvements
<TabItem label="Python">
- ```python
+ ```python title="connect_asana.py"
import scalekit.client, os
from dotenv import load_dotenv
load_dotenv()
connection_name = "asana" # get your connection name from connection configurations
identifier = "user_123" # your unique user identifier
# Get your credentials from app.scalekit.com → Developers → Settings → API Credentials
scalekit_client = scalekit.client.ScalekitClient(
client_id=os.getenv("SCALEKIT_CLIENT_ID"),
client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
env_url=os.getenv("SCALEKIT_ENV_URL"),
)
actions = scalekit_client.actions
# Authenticate the user
link_response = actions.get_authorization_link(
connection_name=connection_name,
identifier=identifier
)
# present this link to your user for authorization, or click it yourself for testing
print("🔗 Authorize Asana:", link_response.link)
input("Press Enter after authorizing...")
# Make a request via Scalekit proxy
- result = actions.request(
- connection_name=connection_name,
- identifier=identifier,
- path="/api/1.0/users/me",
- method="GET"
- )
- print(result)
+ try:
+ result = actions.request(
+ connection_name=connection_name,
+ identifier=identifier,
+ path="/api/1.0/users/me",
+ method="GET"
+ )
+ print(result)
+ except Exception as e:
+ # Handle API errors (e.g., token expired, invalid permissions)
+ print(f"Request failed: {e}")
```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/content/docs/reference/agent-connectors/asana.mdx` around lines 183 -
218, The Python example lacks a code-block title and does not show error
handling for the proxy request; update the fenced code block to include a title
attribute (e.g., ```python title="connect_asana.py"```) and wrap the call to
actions.request (the request to "/api/1.0/users/me") in a try/except that prints
a clear error message on exception (e.g., catch Exception as e and print a
descriptive "Request failed" message), leaving the existing calls to
scalekit.client.ScalekitClient, actions.get_authorization_link, connection_name,
and identifier unchanged.
Comment on lines
+181
to
+216
| <TabItem label="Python"> | ||
| ```python | ||
| import scalekit.client, os | ||
| from dotenv import load_dotenv | ||
| load_dotenv() | ||
|
|
||
| connection_name = "clickup" # get your connection name from connection configurations | ||
| identifier = "user_123" # your unique user identifier | ||
|
|
||
| # Get your credentials from app.scalekit.com → Developers → Settings → API Credentials | ||
| scalekit_client = scalekit.client.ScalekitClient( | ||
| client_id=os.getenv("SCALEKIT_CLIENT_ID"), | ||
| client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"), | ||
| env_url=os.getenv("SCALEKIT_ENV_URL"), | ||
| ) | ||
| actions = scalekit_client.actions | ||
|
|
||
| # Authenticate the user | ||
| link_response = actions.get_authorization_link( | ||
| connection_name=connection_name, | ||
| identifier=identifier | ||
| ) | ||
| # present this link to your user for authorization, or click it yourself for testing | ||
| print("🔗 Authorize ClickUp:", link_response.link) | ||
| input("Press Enter after authorizing...") | ||
|
|
||
| # Make a request via Scalekit proxy | ||
| result = actions.request( | ||
| connection_name=connection_name, | ||
| identifier=identifier, | ||
| path="/api/v2/user", | ||
| method="GET" | ||
| ) | ||
| print(result) | ||
| ``` | ||
| </TabItem> |
Contributor
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial
Add title attribute and error handling to code example.
Add a title attribute and error handling for consistency with documentation standards.
♻️ Suggested improvements
<TabItem label="Python">
- ```python
+ ```python title="connect_clickup.py"
import scalekit.client, os
from dotenv import load_dotenv
...
# Make a request via Scalekit proxy
- result = actions.request(
- connection_name=connection_name,
- identifier=identifier,
- path="/api/v2/user",
- method="GET"
- )
- print(result)
+ try:
+ result = actions.request(
+ connection_name=connection_name,
+ identifier=identifier,
+ path="/api/v2/user",
+ method="GET"
+ )
+ print(result)
+ except Exception as e:
+ # Handle API errors (e.g., token expired, invalid permissions)
+ print(f"Request failed: {e}")
```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/content/docs/reference/agent-connectors/clickup.mdx` around lines 181 -
216, Add a title attribute to the Python code block (e.g., ```python
title="connect_clickup.py"```) and wrap the actions.request call in a try/except
to handle API errors; specifically, update the example around actions.request
(and its surrounding print) to catch Exception as e and print a clear error
message (e.g., "Request failed: {e}") so failures like expired tokens or
permission errors are surfaced to the user.
Comment on lines
+178
to
+214
| <TabItem label="Python"> | ||
| ```python | ||
| import scalekit.client, os, json | ||
| from dotenv import load_dotenv | ||
| load_dotenv() | ||
|
|
||
| connection_name = "linear" # get your connection name from connection configurations | ||
| identifier = "user_123" # your unique user identifier | ||
|
|
||
| # Get your credentials from app.scalekit.com → Developers → Settings → API Credentials | ||
| scalekit_client = scalekit.client.ScalekitClient( | ||
| client_id=os.getenv("SCALEKIT_CLIENT_ID"), | ||
| client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"), | ||
| env_url=os.getenv("SCALEKIT_ENV_URL"), | ||
| ) | ||
| actions = scalekit_client.actions | ||
|
|
||
| # Authenticate the user | ||
| link_response = actions.get_authorization_link( | ||
| connection_name=connection_name, | ||
| identifier=identifier | ||
| ) | ||
| # present this link to your user for authorization, or click it yourself for testing | ||
| print("🔗 Authorize Linear:", link_response.link) | ||
| input("Press Enter after authorizing...") | ||
|
|
||
| # Make a GraphQL request via Scalekit proxy | ||
| result = actions.request( | ||
| connection_name=connection_name, | ||
| identifier=identifier, | ||
| path="/graphql", | ||
| method="POST", | ||
| body=json.dumps({"query": "{ viewer { id name email } }"}) | ||
| ) | ||
| print(result) | ||
| ``` | ||
| </TabItem> |
Contributor
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial
Add title attribute and error handling to code example.
Add a title attribute and wrap the API call in error handling for consistency with documentation standards.
♻️ Suggested improvements
<TabItem label="Python">
- ```python
+ ```python title="connect_linear.py"
import scalekit.client, os, json
from dotenv import load_dotenv
load_dotenv()
...
# Make a GraphQL request via Scalekit proxy
- result = actions.request(
- connection_name=connection_name,
- identifier=identifier,
- path="/graphql",
- method="POST",
- body=json.dumps({"query": "{ viewer { id name email } }"})
- )
- print(result)
+ try:
+ result = actions.request(
+ connection_name=connection_name,
+ identifier=identifier,
+ path="/graphql",
+ method="POST",
+ body=json.dumps({"query": "{ viewer { id name email } }"})
+ )
+ print(result)
+ except Exception as e:
+ # Handle API errors (e.g., token expired, invalid permissions)
+ print(f"Request failed: {e}")
```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/content/docs/reference/agent-connectors/linear.mdx` around lines 178 -
214, Add a title attribute to the Python code block (e.g.,
title="connect_linear.py") and wrap the API call to actions.request in a
try/except to catch and log errors; update the TabItem's Python example around
the actions.request call (where actions.request is invoked with connection_name,
identifier, path="/graphql", method="POST", body=...) to print the result on
success and print or log the exception on failure so the example shows basic
error handling.
Collaborator
Collaborator
Author
|
Closing in favor of #455 which covers Asana, ClickUp, and Linear as part of a broader upgrade to all 35+ agent connector docs with actual screenshots and a templated setup approach. |
Pranesh-Raghu
added a commit
to Pranesh-Raghu/developer-docs
that referenced
this pull request
Mar 2, 2026
…onnectors Ports changes from scalekit-inc#454 — adds Python (and commented Node.js) usage examples and Tool list sections to all three connector docs. Co-Authored-By: Claude Sonnet 4.6 <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
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