feat: guest invites #1290
Merged
feat: guest invites #1290
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
vladfrangu
requested changes
Jul 2, 2025
Jiralite
previously requested changes
Jul 23, 2025
Member
Jiralite
left a comment
Jiralite
left a comment
There was a problem hiding this comment.
joined_at still needs updating to be nullable, no?
Jiralite
force-pushed
the
feat/guest-invites
branch
from
06fc2ad to
368a1f3
Compare
vladfrangu
previously requested changes
Aug 4, 2025
Qjuh
approved these changes
Aug 4, 2025
Member
Qjuh
left a comment
Qjuh
left a comment
There was a problem hiding this comment.
Apart from the change vlad already mentioned this LGTM
Jiralite
approved these changes
Aug 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please describe the changes this PR makes and why it should be merged:
If applicable, please reference Discord API Docs PRs or commits that influenced this PR: