Fixed create link issue #1277
Merged
Fixed create link issue #1277
Conversation
This file contains 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
|
@AshishViradiya153 is attempting to deploy a commit to the mftsio Team on Vercel. A member of the Team first needs to authorize it. |
AshishViradiya153
force-pushed
the
hotFix/1275
branch
from
ccd6083
to
c8f02ca
Compare
|
@mfts Sorry, I made a mistake and misunderstood. The issue isn’t everywhere! I just didn't run the migration, and it only appears in four places where team Id is missing. |
|
Yup that's what I thought. There isn't a good way to indicate when to run a migration or when a migration change happened |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Awarding AshishViradiya153: 150 points 🕹️ Well done! Check out your new contribution on oss.gg/AshishViradiya153 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
fixed #1275
@mfts Fixed now!
I encountered this error, but after removing the .next folder and node_modules, it was resolved!
If this issue arises again in the future.