chore: Updated 8 use unkey blog.md

[Atharva-3000]

Added my own entry

What does this PR do?

Added an entry to the Blog Markdown file with my own blog.

Fixes #2490

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

Here is the Link:

https://dev.to/atharva3000/unkey-rate-limiting-made-super-easy-and-how-i-used-it-2kca

Preview

Summary by CodeRabbit

• New Features
  • Updated blog entry with a new date and author information.
  • Added a link to a new blog post titled "Unkey Rate Limiting Made Super Easy and How I Used It."
• Documentation
  • Revised the structure of the blog post submission format to include the new entry.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7afe894

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]

@Atharva-3000 is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

[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)
dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 18, 2024 2:34pm
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 18, 2024 2:34pm
workflows	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 18, 2024 2:34pm
www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 18, 2024 2:34pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates a blog entry in a document, changing the date from "01-October-2024" to "18-October-2024" and updating the author's name to "Atharva Deshmukh" with a link to their profile. Additionally, a new blog link is included, directing readers to a post titled "Unkey Rate Limiting Made Super Easy and How I Used It" on dev.to. The overall structure of the document remains unchanged.

Changes

Files	Change Summary
oss.gg/8_use_unkey_blog.md	Updated blog entry date and author name; added a new blog link to dev.to post.

Assessment against linked issues

Objective	Addressed	Explanation
Use Unkey in your app and write a blog post about it. (#[2490])	✅

Possibly related issues

• [oss.gg hackathon] Integrated unkey's ratelimiter into my project and wrote a blog post on the same #2346: This issue involves integrating Unkey's ratelimiter into a project and writing a blog post about it, similar to the objectives of this PR.

Possibly related PRs

• feat: Example app showcasing cost based unkey ratelimiting #2231: This PR includes a new entry related to "Cost Based ratelimiting," which is relevant to the blog post submission format updated in the main PR.
• feat: Create a template with Unkey #2272: Similar to feat: Example app showcasing cost based unkey ratelimiting #2231, this PR also features a new entry for "Cost Based ratelimiting," indicating a direct connection to the changes made in the main PR.
• chore: Rust + Rocket template [SIDE QUEST] #2286: This PR adds an entry for "Cost Based ratelimiting," further linking it to the updates in the main PR regarding blog entries.
• feat: Unkey FastAPI boilerplate [SIDE QUEST] #2307: This PR includes an entry for "Cost Based ratelimiting," which aligns with the changes made in the main PR regarding blog entries.
• chore: Next.js Pay-as-you-Go starter kit [SIDE QUEST] #2358: This PR introduces a new entry for "Cost Based ratelimiting," which is directly related to the updates in the main PR regarding blog submissions.

Suggested labels

Needs Approval, 🕹️ oss.gg

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 62df070 and 7afe894.

📒 Files selected for processing (1)

• oss.gg/8_use_unkey_blog.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• oss.gg/8_use_unkey_blog.md

---

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.

[oss-gg]

Awarding Atharva-3000: 1500 points 🕹️ Well done! Check out your new contribution on oss.gg/Atharva-3000