You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal:
The command nhost config pull should not be run if an nhost folder does not exist in the project directory and should prompt the user to run nhost init --remote first.
Reason:
I linked a Nhost cloud project with my GitHub project and it provides a warning on the website to run nhost config pull to get the most recent settings. I ran this but it only created my nhost directory and .toml file and did not pull migrations which I thought it would do. Furthermore I didn't realize init was for existing projects too and thought it was only for initializing projects.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Proposal:
The command
nhost config pull
should not be run if annhost
folder does not exist in the project directory and should prompt the user to runnhost init --remote
first.Reason:
I linked a Nhost cloud project with my GitHub project and it provides a warning on the website to run
nhost config pull
to get the most recent settings. I ran this but it only created mynhost
directory and.toml
file and did not pull migrations which I thought it would do. Furthermore I didn't realizeinit
was for existing projects too and thought it was only for initializing projects.Relevant Discord discussion: https://discord.com/channels/552499021260914688/1211357972291387473
The text was updated successfully, but these errors were encountered: