docs: Quest complete

[ShreyasLakhani]

What does this PR do?

Fixes # (issue)

If there is not an issue for this, please create one first. This is used to tracking purposes and also helps use understand why this PR exists

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

Summary by CodeRabbit

• New Features

  • Added new participant entries for Shreyans Lakhani in both the "Follow the Unkey X account" and "Starry-eyed Supporter" documents, dated 30-October-2024.
  • Included links to Shreyans Lakhani's X account in the relevant sections.

• Documentation

  • Updated documentation to reflect new entries without altering existing functionality or structure.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 66d0dcd

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

[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	Oct 30, 2024 0:28am

[vercel]

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

A member of the Team first needs to authorize it.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The pull request updates two documents by adding new entries for a user named Shreyans Lakhani. In the "Follow the Unkey X account" document, the entry includes the user's submission date and a link to their X account. Similarly, the "Starry-eyed Supporter" document also features a new entry for Shreyas Lakhani, confirming participation in the side quest. These changes do not alter the existing functionality or structure of the documents.

Changes

File Path	Change Summary
oss.gg/3_follow_the_unkey_x_account.md	Added entry for Shreyans Lakhani, dated 30-October-2024, with a link to X account.
oss.gg/4_starry_eyed_supporter.md	Added entry for Shreyas Lakhani, dated 30-October-2024, confirming participation in the quest.

Possibly related PRs

• feat: Follow the Unkey X account #2240: Adds a new entry under the "Follow the Unkey X account" section.
• feat: follow unkey on X #2252: Includes a new entry for Harsh Bhat in the same section.
• feat: follow unkey on X #2252 #2315: Adds an entry for Shreenarayan Jaiswal, relevant to the same section.
• feat: follow unkey on X #2323: Adds an entry for Emily M. Ahtunan, related to the same section.
• Follow the Unkey X account: @unkeydev Complete! #2332: Includes a new entry for Chirag Arora, relevant to the same section.
• Update 3_follow_the_unkey_x_account.md #2338: Adds an entry for Devang Rakholiya, related to the same section.
• docs: Update Followed unkey on X/twitter #2364: Adds an entry for Atharva Deshmukh, relevant to the same section.
• oss.gg side quest 3_follow_the_unkey_x_account.md #2399: Includes a new entry for Ayan Mondal, related to the same section.
• feat: Following unkey acc on twitter #2407 #2408: Adds an entry for Kunal Arya, relevant to the same section.
• Chore/add line to oss gg file #2456: Adds an entry for Zia Ur Rehman, related to the same section.

Suggested labels

Needs Approval, 🕹️ oss.gg, :joystick: 50 points, :joystick: 150 points

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! 🙏

[ShreyasLakhani]

@chronark now review. there are only two files and no deleted