docs: Update 3_follow_the_unkey_x_account.md file

[arg387]

What does this PR do?

Include my name to Update 3_follow_the_unkey_account.md

Fixes

Only add my name to the given md file

Points

I have already got the points. So i don't want that.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• Enhancement (small improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How should this be tested?

• Test A
• Test B

Checklist

Required

• Filled out the "How to test" section in this PR
• Read Contributing Guide
• Self-reviewed my own code
• Commented on my code in hard-to-understand areas
• Ran pnpm build
• Ran pnpm fmt
• Checked for warnings, there are none
• Removed all console.logs
• Merged the latest changes from main onto my branch with git pull origin main
• My changes don't cause any responsiveness issues

Appreciated

• If a UI change was made: Added a screen recording or screenshots to this PR
• Updated the Unkey Docs if changes were necessary

Proof

If you need the screenshot please ask me in comment.

Summary by CodeRabbit

• New Features

  • Added a new participant entry for the side quest "Follow the Unkey X account" featuring Argha Saha, including a link to their X account.

• Documentation

  • Updated the document to maintain consistency with previous entries.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9fa8093

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

📝 Walkthrough

📝 Walkthrough

Walkthrough

The pull request updates the document "Follow the Unkey X account" by adding a new entry for participant Argha Saha, dated 27-October-2024. This entry includes a link to their X account and follows the established format of previous entries, ensuring consistency within the document.

Changes

File Path	Change Summary
oss.gg/3_follow_the_unkey_x_account.md	Added new entry for Argha Saha with date and X account link.

Possibly related PRs

• feat: Follow the Unkey X account #2240: Updates the same document by replacing an entry in the "Follow the Unkey X account" side quest.
• feat: follow unkey on X #2252: Adds a new entry for a participant in the same side quest.
• feat: follow unkey on X #2252 #2315: Adds a new entry for a participant in the same side quest.
• feat: follow unkey on X #2323: Adds another new entry for a participant in the same side quest.
• Update 3_follow_the_unkey_x_account.md #2324: Adds a new entry for a participant in the same side quest.
• Follow the Unkey X account: @unkeydev Complete! #2332: Adds a new entry for a participant in the same side quest.
• Update 3_follow_the_unkey_x_account.md #2338: Adds a new entry for a participant in the same side quest.
• feat: follow unkey on X #2357: Adds a new entry for a participant in the same side quest.
• docs: Update Followed unkey on X/twitter #2364: Adds a new entry for a participant in the same side quest.
• oss.gg side quest 3_follow_the_unkey_x_account.md #2399: Adds a new entry for a participant in the same side quest.
• feat: Following unkey acc on twitter #2407 #2408: Adds a new entry for a participant in the same side quest.

Suggested labels

Needs Approval, 🕹️ oss.gg

Suggested reviewers

• mcstepp
• chronark
• perkinsjr
• MichaelUnkey

---

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.

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 2, 2024 3:46pm

[vercel]

@arg387 is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.