Feat/ automated thank you message

[Aditya8369]

Summary

Created a new GitHub Actions workflow at .github/workflows/issue-resolved-thanks.yml

Related Issue

Closes #330

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor
• Chore / dependency update

Changes Made

• The workflow triggers on the issues.closed event and targets non-bot creators.
• It uses a condition github.event.issue.state_reason == 'completed' to ensure the action only runs when the issue is resolved successfully

AI Usage

• I did not use AI for any part of the code in this PR
• I used AI for coding (specify which tool below) and I fully understand every change I made, including which functions I changed, why I changed them, and what side effects they could create

[github-actions]

Welcome to OSSfolio, @Aditya8369! 🎉

Thank you for opening this pull request and contributing to the open-source community! 🚀

To ensure a smooth review process, please make sure you have:

• Checked that your changes work locally and compile cleanly.
• Followed the guidelines outlined in CONTRIBUTING.md.
• Linked your PR to an open issue (e.g. Closes #ISSUE_NUMBER).

We will review your PR as soon as possible. Happy coding! 💻✨

[coderabbitai]

Warning

Review limit reached

@Aditya8369, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 75ad9328-be9a-4d52-99c8-b5fb83cfe761

📥 Commits

Reviewing files that changed from the base of the PR and between 8626d3b and 41e5be7.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• .github/workflows/issue-resolved-thanks.yml
• src/components/profile/ProfileActions.tsx
• src/components/profile/ProfileView.tsx
• src/lib/score.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[PRODHOSH]

pls check this pr has unnessecary code and merge conflicts @Aditya8369

[PRODHOSH]

@Aditya8369 any updates?
there is unnessecarry code in this pr remove all that
have only the workflow code