-
Notifications
You must be signed in to change notification settings - Fork 529
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
Follow the Unkey X account #2442
Conversation
|
|
@rajeevDewangan is attempting to deploy a commit to the Unkey Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughThe pull request updates the document Changes
Possibly related PRs
Suggested labels
Suggested reviewers
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 (
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Details:
|
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: 0
🧹 Outside diff range and nitpick comments (1)
oss.gg/3_follow_the_unkey_x_account.md (1)
55-57
: LGTM! Consider enclosing the URL in angle brackets.The new entry for Rajeev Dewangan follows the correct format and is in the proper chronological order. Well done!
To improve markdown practices and address the Markdownlint warning, consider enclosing the URL in angle brackets:
» 15-October-2024 by [Rajeev Dewangan](@rajeevdew) -» Link to Account: https://x.com/rajeevdew +» Link to Account: <https://x.com/rajeevdew>This change would make the URL format consistent with some of the previous entries (e.g., Chirag Arora's entry) and follow better markdown practices.
🧰 Tools
🪛 Markdownlint
56-56: null
Bare URL used(MD034, no-bare-urls)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- oss.gg/3_follow_the_unkey_x_account.md (1 hunks)
🧰 Additional context used
🪛 Markdownlint
oss.gg/3_follow_the_unkey_x_account.md
56-56: null
Bare URL used(MD034, no-bare-urls)
🔇 Additional comments (1)
oss.gg/3_follow_the_unkey_x_account.md (1)
Line range hint
1-57
: Overall, the changes look good!The new entry for Rajeev Dewangan has been added correctly, following the established format and maintaining chronological order. The only minor suggestion is to enclose the URL in angle brackets for better markdown practices.
🧰 Tools
🪛 Markdownlint
53-53: null
Bare URL used(MD034, no-bare-urls)
56-56: null
Bare URL used(MD034, no-bare-urls)
/award 50 |
Awarding rajeevDewangan: 50 points 🕹️ Well done! Check out your new contribution on oss.gg/rajeevDewangan |
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
Summary by CodeRabbit