Skip to content

Conversation

@pixelfact
Copy link
Contributor

@pixelfact pixelfact commented Mar 31, 2025

Summary by CodeRabbit

  • New Features
    • Updated the contributions view to automatically filter out linked issues, streamlining the displayed results for a clearer overview of contributions.

@pixelfact pixelfact self-assigned this Mar 31, 2025
@linear
Copy link

linear bot commented Mar 31, 2025

@vercel
Copy link

vercel bot commented Mar 31, 2025

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

Name Status Preview Comments Updated (UTC)
saas-frontend ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 31, 2025 3:04pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 31, 2025

Walkthrough

This change updates the dashboard contributions page by adding a new boolean property, showLinkedIssues, to the queryParams object within the MyDashboardContributionsPage function in the contributions page file. The property is set to false, ensuring that linked issues are not displayed in the contributions query, while all other existing parameters remain unchanged.

Changes

File Change Summary
app/(saas)/.../page.tsx Added the showLinkedIssues: false property to the queryParams object in MyDashboardContributionsPage to adjust the contributions filter.

Suggested reviewers

  • haydencleary

Poem

In fields of code, I hop with glee,
Adding tweaks as quick as can be.
Bugs beware, the changes are in sight,
With new flags shining oh so bright.
Hooray for progress—let's code tonight!
🐇💨


📜 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 2c29ea5 and 82819c5.

📒 Files selected for processing (1)
  • app/(saas)/my-dashboard/contributions/page.tsx (1 hunks)
🔇 Additional comments (1)
app/(saas)/my-dashboard/contributions/page.tsx (1)

40-40: Addition of showLinkedIssues parameter looks good.

The addition of this parameter to filter out linked issues from the dashboard contributions view makes sense and is well-placed within the queryParams object. The parameter is correctly typed as part of the GetContributionsQueryParams interface.

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@pixelfact pixelfact merged commit 4766e68 into main Mar 31, 2025
4 of 5 checks passed
@pixelfact pixelfact deleted the sb-59-fix-bug-add-showlinkedissuesfalse-in-get-v1contributions branch March 31, 2025 15:05
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