FIX GIVback eligibility option for admin actions

[mateodaza]

Summary by CodeRabbit

• New Features

  • Updated project verification logic to focus on Givback eligibility.
  • Modified labels in the project actions to reflect Givback eligibility status.

• Bug Fixes

  • Improved control flow for determining verification options based on new eligibility criteria.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
giveth-dapps-v2	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Sep 26, 2024 2:47am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request focus on updating the AdminActions and ProjectActions components to replace the verified property with isGivbackEligible. This adjustment modifies the logic for determining project verification status, shifting the focus from verification to Givback eligibility. The updates affect how verification is disabled and how options are presented to users regarding project actions.

Changes

File Path	Change Summary
src/components/views/project/projectActionCard/AdminActions.tsx	Updated destructured properties to replace verified with isGivbackEligible, altering verification logic.
src/components/views/userProfile/projectsTab/ProjectActions.tsx	Modified conditional logic to check Givback eligibility instead of verification status, updating labels accordingly.

Possibly related PRs

• Fixed verify project on project actions dropdown menu #4455: This PR modifies the conditional logic in ProjectActions.tsx to refine how project verification status is checked, aligning with the changes in the main PR that also shifts focus from verified to isGivbackEligible.
• Decentralized Verification Feedback: Badges Tooltips + Filters #4765: This PR updates the ProjectStats.tsx and ProjectItem.tsx components to use isGivbackEligible instead of verified, directly relating to the changes made in the main PR regarding the verification logic.

Suggested reviewers

• MohammadPCh

Poem

In the garden where projects bloom,
Givback eligibility clears the gloom.
With a hop and a skip, we change the way,
Verification's past, it's a brighter day!
So let’s cheer for the updates, oh what a delight,
A new path for projects, shining so bright! 🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.