-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Linear Project Updates webhook #15259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
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 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. 📒 Files selected for processing (12)
WalkthroughThis pull request introduces a new webhook trigger for Linear project updates. The changes include updating package versions for Changes
Assessment against linked issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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.1Following 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 fieldsThe metadata could be enriched with more project fields to provide better context in the event payload. Fields like
status
,progress
, orpriority
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 fragmentThe
creator
andlead
fields only include theid
. Consider adding more user fields likename
,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.0For 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
⛔ 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
components/linear/sources/project-updated-instant/project-updated-instant.mjs
Outdated
Show resolved
Hide resolved
There was a problem hiding this 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!
Resolves #15239
Summary by CodeRabbit
Version Updates
@pipedream/linear
package from0.5.8
to0.6.0
@pipedream/linear_app
package from0.5.7
to0.6.0
New Features
Improvements
Minor Updates