Skip to content

Conversation

michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Jan 10, 2025

Resolves #15239

Summary by CodeRabbit

  • Version Updates

    • Updated @pipedream/linear package from 0.5.8 to 0.6.0
    • Updated @pipedream/linear_app package from 0.5.7 to 0.6.0
  • New Features

    • Added a new webhook for tracking project updates in Linear
    • Introduced a new GraphQL fragment for enhanced project data handling
    • Enhanced project data retrieval with more detailed GraphQL queries
  • Improvements

    • Expanded project query capabilities with filtering and ordering options
  • Minor Updates

    • Incremented version numbers for various modules without functional changes

Copy link

vercel bot commented Jan 10, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Ignored (Inspect) Visit Preview Jan 10, 2025 7:48pm
pipedream-docs ⬜️ Ignored (Inspect) Jan 10, 2025 7:48pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) Jan 10, 2025 7:48pm

Copy link
Contributor

coderabbitai bot commented Jan 10, 2025

Warning

Rate limit exceeded

@michelle0927 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 13 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 017f73f and 3fadf22.

📒 Files selected for processing (12)
  • components/linear/actions/create-issue/create-issue.mjs (1 hunks)
  • components/linear/actions/get-issue/get-issue.mjs (1 hunks)
  • components/linear/actions/get-teams/get-teams.mjs (1 hunks)
  • components/linear/actions/search-issues/search-issues.mjs (1 hunks)
  • components/linear/actions/update-issue/update-issue.mjs (1 hunks)
  • components/linear/linear.app.mjs (1 hunks)
  • components/linear/sources/comment-created-instant/comment-created-instant.mjs (1 hunks)
  • components/linear/sources/issue-created-instant/issue-created-instant.mjs (1 hunks)
  • components/linear/sources/issue-updated-instant/issue-updated-instant.mjs (1 hunks)
  • components/linear/sources/new-issue-status-updated/new-issue-status-updated.mjs (1 hunks)
  • components/linear/sources/project-updated-instant/project-updated-instant.mjs (1 hunks)
  • components/linear_app/common/queries.mjs (1 hunks)

Walkthrough

This pull request introduces a new webhook trigger for Linear project updates. The changes include updating package versions for @pipedream/linear and @pipedream/linear_app from 0.5.8 and 0.5.7 to 0.6.0 respectively. A new GraphQL fragment for projects has been added, and a new module for project update events has been created. The implementation allows for filtering and retrieving project updates with detailed metadata.

Changes

File Change Summary
components/linear/package.json Version bumped from 0.5.8 to 0.6.0
components/linear_app/package.json Version bumped from 0.5.7 to 0.6.0
components/linear_app/common/fragments.mjs Added new Project GraphQL fragment with comprehensive project fields
components/linear_app/common/queries.mjs Updated listProjects query to support filtering and ordering
components/linear/sources/project-updated-instant/project-updated-instant.mjs New module for project update webhook
components/linear_app/sources/project-updated-instant/project-updated-instant.mjs New module for project update webhook with detailed event handling
components/linear_app/actions/create-issue/create-issue.mjs Version bumped from 0.4.5 to 0.4.6
components/linear_app/actions/get-issue/get-issue.mjs Version bumped from 0.1.5 to 0.1.6
components/linear_app/actions/get-teams/get-teams.mjs Version bumped from 0.2.5 to 0.2.6
components/linear_app/actions/search-issues/search-issues.mjs Version bumped from 0.2.5 to 0.2.6
components/linear_app/actions/update-issue/update-issue.mjs Version bumped from 0.1.5 to 0.1.6
components/linear_app/sources/comment-created-instant/comment-created-instant.mjs Version bumped from 0.1.7 to 0.1.8
components/linear_app/sources/issue-created-instant/issue-created-instant.mjs Version bumped from 0.3.7 to 0.3.8
components/linear_app/sources/issue-updated-instant/issue-updated-instant.mjs Version bumped from 0.3.7 to 0.3.8
components/linear_app/sources/new-issue-status-updated/new-issue-status-updated.mjs Version bumped from 0.1.7 to 0.1.8

Assessment against linked issues

Objective Addressed Explanation
Create Linear Project Updates webhook [#15239]
Support webhook payload processing
Provide detailed project update information

Possibly related PRs

Suggested labels

User submitted

Suggested reviewers

  • GTFalcao

Poem

🐰 Hop, hop, Linear's new dance,
Projects update with a single glance,
Webhooks singing their melodic tune,
Pipedream's magic rises like the moon!
Code leaps forward, version takes flight! 🚀


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (4)
components/linear_app/sources/project-updated-instant/project-updated-instant.mjs (2)

11-11: Consider starting with version 0.1.0 instead of 0.0.1

Following semantic versioning best practices, initial public releases typically start at 0.1.0 to indicate the first minor version.

-  version: "0.0.1",
+  version: "0.1.0",

54-66: Consider enhancing metadata with additional project fields

The metadata could be enriched with more project fields to provide better context in the event payload. Fields like status, progress, or priority could be valuable for consumers.

   getMetadata(resource) {
     const {
       name,
       data,
       updatedAt,
+      status,
+      progress,
+      priority,
     } = resource;
     const ts = Date.parse(data?.updatedAt || updatedAt);
     return {
       id: `${resource.id}-${ts}`,
-      summary: `Project Updated: ${data?.name || name}`,
+      summary: `Project Updated: ${data?.name || name} (Status: ${status?.name || 'N/A'}, Progress: ${progress}%)`,
       ts,
+      status: status?.name,
+      progress,
+      priority,
     };
   },
components/linear_app/common/fragments.mjs (1)

108-113: Consider expanding user-related fields in the Project fragment

The creator and lead fields only include the id. Consider adding more user fields like name, email, or avatarUrl for better context.

       creator {
         id
+        name
+        email
+        avatarUrl
       }
       lead {
         id
+        name
+        email
+        avatarUrl
       }
components/linear/sources/project-updated-instant/project-updated-instant.mjs (1)

13-13: Consider starting with version 0.1.0

For consistency with the base implementation, consider starting with version 0.1.0.

-  version: "0.0.1",
+  version: "0.1.0",
🧰 Tools
🪛 GitHub Actions: Pull Request Checks

[error] Module not found: Cannot find module '@pipedream/linear_app/sources/project-updated-instant/project-updated-instant.mjs'. The required dependency is missing or not properly installed.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 717258a and a5dceb5.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (6)
  • components/linear/package.json (1 hunks)
  • components/linear/sources/project-updated-instant/project-updated-instant.mjs (1 hunks)
  • components/linear_app/common/fragments.mjs (1 hunks)
  • components/linear_app/common/queries.mjs (1 hunks)
  • components/linear_app/package.json (1 hunks)
  • components/linear_app/sources/project-updated-instant/project-updated-instant.mjs (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • components/linear_app/package.json
  • components/linear/package.json
🧰 Additional context used
🪛 GitHub Actions: Pull Request Checks
components/linear/sources/project-updated-instant/project-updated-instant.mjs

[error] Module not found: Cannot find module '@pipedream/linear_app/sources/project-updated-instant/project-updated-instant.mjs'. The required dependency is missing or not properly installed.

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
  • GitHub Check: pnpm publish

Copy link
Collaborator

@luancazarine luancazarine left a comment

Choose a reason for hiding this comment

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

Hi @michelle0927, LGTM! Ready for QA!

@michelle0927 michelle0927 merged commit 34f5a2a into master Jan 15, 2025
10 of 11 checks passed
@michelle0927 michelle0927 deleted the issue-15239 branch January 15, 2025 15:51
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.

[TRIGGER] Linear Project Updates webhook
2 participants