-
Notifications
You must be signed in to change notification settings - Fork 521
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
oss.gg side quest 3_follow_the_unkey_x_account.md #2459
Conversation
|
📝 WalkthroughWalkthroughThe pull request introduces a new entry in the document Changes
Assessment against linked issues
Possibly related issues
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 ↗︎
|
@gauravkharel is attempting to deploy a commit to the Unkey Team on Vercel. A member of the Team first needs to authorize it. |
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
: Enclose the URL in angle brackets for better Markdown formattingThe entry looks good and follows the established schema. However, to improve the Markdown formatting and address the linter warning, please enclose the URL in angle brackets.
Apply this change to line 56:
-» Link to Account: https://x.com/gauravdoux +» Link to Account: <https://x.com/gauravdoux>This change will make the formatting consistent with some of the previous entries and improve the overall document structure.
🧰 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)
55-57
: LGTM! The side quest entry has been successfully added.The new entry for Gaurav Kharel has been correctly added to the document, following the established schema and meeting the objectives of the PR. With the minor formatting adjustment suggested earlier, this change is ready to be merged.
🧰 Tools
🪛 Markdownlint
56-56: null
Bare URL used(MD034, no-bare-urls)
/award 50 |
Awarding gauravkharel: 50 points 🕹️ Well done! Check out your new contribution on oss.gg/gauravkharel |
What does this PR do?
Completed the challenge of side quest: Follow on X
Fixes #2458
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
Screenshot
Summary by CodeRabbit