Skip to content
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

refactor: use unique for clerkId to avoid duplicate user in db #113

Merged

Conversation

jsun969
Copy link
Member

@jsun969 jsun969 commented Feb 28, 2024

Description

Briefly describe the purpose of this pull request.

Changes Made

Provide a list of changes made in this pull request.

Related Issues

Reference any related issues using keywords like "Fixes #issue-number".

Additional Notes

Add any other notes or screenshots that might be helpful for the reviewers.

Copy link

vercel bot commented Feb 28, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
website ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 28, 2024 5:07am

@rayokamoto rayokamoto merged commit 3432c14 into main Mar 8, 2024
4 checks passed
@rayokamoto rayokamoto deleted the refactor/check-user-existance-when-create-using-unique branch March 8, 2024 10:51
jsun969 added a commit that referenced this pull request Mar 15, 2024
* refactor: use `unique` for `clerkId` to avoid duplicate user in db (#113)

* chore: Update committee members (#119)

* refactor(about): committee data type

* chore(about): update committee members

* chore(about): transfer all rep to general committee

* chore(about): update committee
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants