Skip to content

Conversation

michelle0927
Copy link
Collaborator

@michelle0927 michelle0927 commented Oct 6, 2025

Follow-up PR to #18606

Summary by CodeRabbit

  • New Features

    • Added Linear “Create Project” action.
    • Added Linear “List Projects” action.
  • Chores

    • Bumped Linear package version and aligned dependency versions.
    • Incremented versions for existing Linear actions (create issue, get issue, search issues, update issue, get teams).
    • Incremented versions for Linear event sources (comment created, issue created, issue updated, issue status updated, project update created, project updated).

@michelle0927 michelle0927 self-assigned this Oct 6, 2025
Copy link

vercel bot commented Oct 6, 2025

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

2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
pipedream-docs Ignored Ignored Oct 6, 2025 5:03pm
pipedream-docs-redirect-do-not-edit Ignored Ignored Oct 6, 2025 5:03pm

Copy link
Contributor

coderabbitai bot commented Oct 6, 2025

Walkthrough

Adds two new Linear actions (create-project, list-projects) that re-export base actions with app props and metadata. Bumps versions across several existing Linear actions and sources. Updates components/linear package version and its @pipedream/linear_app dependency. No logic changes beyond new action wrappers.

Changes

Cohort / File(s) Summary
New Linear actions (re-export + app props)
components/linear/actions/create-project/create-project.mjs, components/linear/actions/list-projects/list-projects.mjs
New default exports that spread base actions from @pipedream/linear_app, add utils.getAppProps(...), set key, description (with docs links), and version set to "0.0.1".
Action version bumps
components/linear/actions/create-issue/create-issue.mjs, components/linear/actions/get-issue/get-issue.mjs, components/linear/actions/get-teams/get-teams.mjs, components/linear/actions/search-issues/search-issues.mjs, components/linear/actions/update-issue/update-issue.mjs
Incremented version fields only. No behavioral changes.
Source version bumps
components/linear/sources/comment-created-instant/comment-created-instant.mjs, components/linear/sources/issue-created-instant/issue-created-instant.mjs, components/linear/sources/issue-updated-instant/issue-updated-instant.mjs, components/linear/sources/new-issue-status-updated/new-issue-status-updated.mjs, components/linear/sources/new-projectupdate-created/new-projectupdate-created.mjs, components/linear/sources/project-updated-instant/project-updated-instant.mjs
Incremented version fields only. No functional changes.
Package metadata
components/linear/package.json
Bumps package version 0.7.5 → 0.8.0 and updates @pipedream/linear_app dependency ^0.7.5 → ^0.8.0.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant U as User
  participant A as Pipedream Action: Create Project
  participant L as Linear API

  U->>A: Provide project input + auth
  A->>L: POST ProjectCreateInput
  L-->>A: Project data / error
  A-->>U: Emit result
  Note over A,L: New wrapper re-exports base action with app props
Loading
sequenceDiagram
  autonumber
  participant U as User
  participant A as Pipedream Action: List Projects
  participant L as Linear API

  U->>A: Provide pagination/filter + auth
  A->>L: Query Projects
  L-->>A: ProjectConnection
  A-->>U: Emit list
  Note over A,L: New wrapper re-exports base action with app props
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • luancazarine
  • GTFalcao

Poem

A rabbit taps out tidy commits today,
Two fresh paths to projects—hip hooray!
Versions hop a notch, neat and light,
Packages nudged, dependencies right.
With whiskers twitching, I merge with cheer—
Linear lines, now crisp and clear. 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description only references a previous PR and does not follow the repository’s required template, which expects a “## WHY” section explaining the motivation and context for the changes. As a result, reviewers lack the necessary background to assess the purpose and impact of these updates. The absence of any additional detail or justification means the description is largely incomplete. Update the pull request description to include the required “## WHY” section and provide a concise summary of the motivation, goals, and high-level overview of the changes introduced in this follow-up PR.
Title Check ❓ Inconclusive The title “Linear - updates and new components” is very general and does not clearly convey which specific updates or new components are included, making it hard for reviewers to understand the primary focus at a glance. Although it hints at version bumps and added actions, it lacks detail about the most significant changes in this PR. A more descriptive title would improve clarity and help teammates quickly grasp the main purpose of the changeset. Please revise the title to succinctly reflect the key changes, for example by mentioning the version bumps and the addition of new create-project and list-projects actions, so that readers immediately understand the primary purpose of this pull request.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch issue-18600-2

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d268b9a and 5f387b8.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (14)
  • components/linear/actions/create-issue/create-issue.mjs (1 hunks)
  • components/linear/actions/create-project/create-project.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/list-projects/list-projects.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/package.json (2 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/new-projectupdate-created/new-projectupdate-created.mjs (1 hunks)
  • components/linear/sources/project-updated-instant/project-updated-instant.mjs (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Verify TypeScript components
  • GitHub Check: Publish TypeScript components
  • GitHub Check: pnpm publish
  • GitHub Check: Lint Code Base
🔇 Additional comments (16)
components/linear/sources/issue-created-instant/issue-created-instant.mjs (1)

13-13: Version bump only — LGTM

Consistent with package updates. No functional changes.

components/linear/sources/new-projectupdate-created/new-projectupdate-created.mjs (1)

14-14: Version bump only — LGTM

Matches the ecosystem-wide minor bumps. No behavior change.

components/linear/actions/create-issue/create-issue.mjs (1)

13-13: Version bump only — LGTM

Wrapper export unchanged; metadata updated.

components/linear/actions/get-issue/get-issue.mjs (1)

13-13: Version bump only — LGTM

No logic changes; metadata aligns with package updates.

components/linear/package.json (1)

3-3: Approve version bump
Confirmed @pipedream/linear v0.8.0 and @pipedream/linear_app ^0.8.0 exist on npm and key import paths return HTTP 200.

components/linear/sources/comment-created-instant/comment-created-instant.mjs (1)

13-13: LGTM! Version bump aligns with dependency update.

The version increment is appropriate and coordinates with the broader package update.

components/linear/actions/update-issue/update-issue.mjs (1)

12-12: LGTM! Version bump aligns with dependency update.

The version increment is appropriate and coordinates with the broader package update.

components/linear/actions/get-teams/get-teams.mjs (1)

13-13: LGTM! Version bump aligns with dependency update.

The version increment is appropriate and coordinates with the broader package update.

components/linear/sources/project-updated-instant/project-updated-instant.mjs (1)

14-14: LGTM! Version bump aligns with dependency update.

The version increment is appropriate and coordinates with the broader package update.

components/linear/actions/search-issues/search-issues.mjs (1)

13-13: LGTM! Version bump aligns with dependency update.

The version increment is appropriate and coordinates with the broader package update.

components/linear/sources/new-issue-status-updated/new-issue-status-updated.mjs (1)

13-13: LGTM! Version bump aligns with dependency update.

The version increment is appropriate and coordinates with the broader package update.

components/linear/sources/issue-updated-instant/issue-updated-instant.mjs (1)

13-13: LGTM! Version bump aligns with dependency update.

The version increment is appropriate and coordinates with the broader package update.

components/linear/actions/create-project/create-project.mjs (1)

1-14: LGTM! New action wrapper follows established pattern.

The implementation correctly follows the established pattern for Linear action wrappers in this codebase. The component properly imports the base action from @pipedream/linear_app, augments it with app props via utils.getAppProps(), and provides appropriate metadata.

components/linear/actions/list-projects/list-projects.mjs (3)

1-2: LGTM!

The imports are clean and follow the established pattern for re-exporting base actions with app-specific augmentations.


4-6: ESLint disables are appropriate for this wrapper pattern.

The disabled rules are necessary because required properties (type, name, version) are provided through spread operators rather than explicit declarations, which is the standard pattern for Pipedream component wrappers.


8-14: LGTM!

The export structure is well-organized:

  • Spread order ensures proper property precedence (base → app props → explicit overrides)
  • Key naming follows Pipedream conventions
  • Documentation link appropriately references Linear's GraphQL API schema
  • Version correctly set to 0.0.1 for a new component

This implementation is consistent with the established pattern across other Linear actions in this PR.


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.

@michelle0927 michelle0927 moved this from Doing to Ready for PR Review in Component (Source and Action) Backlog Oct 6, 2025
@luancazarine luancazarine moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog Oct 7, 2025
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!

@luancazarine luancazarine moved this from In Review to Ready for QA in Component (Source and Action) Backlog Oct 7, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to Ready for Release in Component (Source and Action) Backlog Oct 8, 2025
@vunguyenhung
Copy link
Collaborator

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/Linear-updates-and-new-components-285bf548bb5e81abb1d8f7e3765e2caa

@vunguyenhung vunguyenhung merged commit 667cc73 into master Oct 8, 2025
10 checks passed
@vunguyenhung vunguyenhung deleted the issue-18600-2 branch October 8, 2025 01:55
@github-project-automation github-project-automation bot moved this from Ready for Release to Done in Component (Source and Action) Backlog Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants