-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Update 8_use_unkey_blog.md #2500
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📝 Walkthrough📝 WalkthroughWalkthroughThe changes involve the addition of a new blog entry to the existing list in the file Changes
Possibly related PRs
Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@utkarshml is attempting to deploy a commit to the Unkey Team on Vercel. A member of the Team first needs to authorize it. |
Thank you for following the naming conventions for pull request titles! 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (1)
oss.gg/8_use_unkey_blog.md (1)
25-26
: LGTM! Minor formatting suggestion.The new entry adheres to the required format and provides all necessary information. It's correctly placed in chronological order. Great job!
A minor suggestion to improve consistency:
Consider adjusting the spacing in "App Link :" to match the format of "Blog Link:". Here's the suggested change:
-» 19-October-2024 by [Utkarsh Jaiswal](https://oss.gg/utkarshml) Blog Link: [Blog](https://readwithutkarsh.hashnode.dev/protecting-your-api-with-unkey-a-guide-to-api-security-and-rate-limiting) App Link : [Github Repo](https://github.com/utkarshml/unkey_application) +» 19-October-2024 by [Utkarsh Jaiswal](https://oss.gg/utkarshml) Blog Link: [Blog](https://readwithutkarsh.hashnode.dev/protecting-your-api-with-unkey-a-guide-to-api-security-and-rate-limiting) App Link: [Github Repo](https://github.com/utkarshml/unkey_application)
Hey @utkarshml, this issue is specifically for using Unkey in your product in production, which this post does not mention at all. |
Update my blog based on your feedback
Hey @chronark , i update my blog based on your feedback |
/award 1500 |
Awarding utkarshml: 1500 points 🕹️ Well done! Check out your new contribution on oss.gg/utkarshml |
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
How should this be tested?
Checklist
Required
pnpm build
pnpm fmt
console.logs
git pull origin main
Appreciated
Here is the Link:
(https://readwithutkarsh.hashnode.dev/rate-limiting-on-product-search-in-e-commerce-with-unkey)
Summary by CodeRabbit