docs: Update Supabase dashboard instructions #72
Merged
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
|
@kamilogorek is attempting to deploy a commit to the Leap AI Team on Vercel. A member of the Team first needs to authorize it. |
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.
Currently project id is not updated during initial clone of the repository, thus leaving it as
{projectId}which leads toThis project does not existerror and might make people confused.For now more clear instructions are fine, but preferable it'd pull
projectIdduring setup flow and make appropriate commit to the cloned repository, making the direct link work as expected.Note that if it's changed to "post clone" update, readme guide on integrations page would not work anyway, so maybe just updating the wording to the one above is even better.