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

Do not run "config pull" unless project initialized #838

Open
lectrician1 opened this issue Feb 27, 2024 · 1 comment
Open

Do not run "config pull" unless project initialized #838

lectrician1 opened this issue Feb 27, 2024 · 1 comment

Comments

@lectrician1
Copy link

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.

Relevant Discord discussion: https://discord.com/channels/552499021260914688/1211357972291387473

Copy link

stale bot commented Aug 25, 2024

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.

@stale stale bot added the stale label Aug 25, 2024
@dbarrosop dbarrosop removed the stale label Aug 26, 2024
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

No branches or pull requests

2 participants