[🕹️] Starry Eye Submission

[AkashJana18]

What does this PR do?

Starry Eye Submission

Points : 150

Summary by CodeRabbit

• New Features
  • Updated the "Your turn" section in the document to include a new entry for user Akash Jana, enhancing participation records for the side quest.
  • Added a link to a relevant GitHub issue for better tracking and engagement.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 030bd03

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 28, 2024 6:01pm

[vercel]

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

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the document oss.gg/4_starry_eyed_supporter.md by adding a new entry under the "Your turn" section. The entry includes the name Akash Jana and a link to a specific GitHub issue. The existing entries in the document remain unchanged, and no alterations were made to the declarations of exported or public entities.

Changes

File	Change Summary
oss.gg/4_starry_eyed_supporter.md	Added new entry for Akash Jana with a GitHub link

Possibly related PRs

• feat: Follow the Unkey X account #2240: Updates the document oss.gg/3_follow_the_unkey_x_account.md to reflect a new entry.
• feat: follow unkey on X #2252: Modifies the document oss.gg/3_follow_the_unkey_x_account.md by adding a new entry.
• feat: follow unkey on X #2252 #2315: Updates the document oss.gg/3_follow_the_unkey_x_account.md with a new entry.
• feat: follow unkey on X #2323: Adds a new entry to the document oss.gg/3_follow_the_unkey_x_account.md.
• Update 3_follow_the_unkey_x_account.md #2324: Updates the document oss.gg/3_follow_the_unkey_x_account.md with a new entry.
• docs: Update Followed unkey on X/twitter #2364: Adds a new entry to the document oss.gg/3_follow_the_unkey_x_account.md.
• oss.gg side quest 3_follow_the_unkey_x_account.md #2399: Updates the document oss.gg/3_follow_the_unkey_x_account.md with a new entry.
• Chore/add line to oss gg file #2456: Updates both oss.gg/4_starry_eyed_supporter.md and oss.gg/3_follow_the_unkey_x_account.md.

Suggested labels

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

Suggested reviewers

• mcstepp
• chronark
• perkinsjr
• MichaelUnkey

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8fb9d4d and 030bd03.

📒 Files selected for processing (1)

• oss.gg/4_starry_eyed_supporter.md (1 hunks)

🧰 Additional context used

🪛 Markdownlint

oss.gg/4_starry_eyed_supporter.md

31-31: null
Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)

oss.gg/4_starry_eyed_supporter.md (1)

30-32: LGTM! Entry format is consistent.

The new entry follows the established format with date, name, and issue link.

Let's verify the side quest requirements:

✅ Verification successful

Verification successful - Entry and requirements are valid

The verification confirms:

• Account age requirement met (created: April 10, 2022, >1 year old)
• Issue contains 6 screenshots showing friend confirmations and stars
• Issue is properly labeled and formatted

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the linked issue contains required proof and account age

# Test 1: Fetch the issue content to verify screenshots and confirmations
gh issue view 2570 --repo unkeyed/unkey

# Test 2: Check account creation date to verify >1 year requirement
gh api -H "Accept: application/vnd.github+json" /users/AkashJana18 | jq .created_at

Length of output: 1287

🧰 Tools

🪛 Markdownlint

31-31: null
Bare URL used

(MD034, no-bare-urls)

---

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]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Here is an example:

<type>[optional scope]: <description>
fix: I fixed something for Unkey

Details:

No release type found in pull request title "[🕹️] Starry Eye Submission". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[chronark]

closing this, the issue is sufficient to track