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

graphile-migrate watch --once is hard to discover #139

Open
2 tasks
benjie opened this issue Sep 15, 2021 · 2 comments
Open
2 tasks

graphile-migrate watch --once is hard to discover #139

benjie opened this issue Sep 15, 2021 · 2 comments

Comments

@benjie
Copy link
Member

benjie commented Sep 15, 2021

When you run graphile-migrate --help there's no hint that watch --once exists, and the description for watch doesn't seem like what you need.

Suggestions:

  • Update the watch description so it also covers the --once use case
  • Consider adding a command alias (identical to calling graphile-migrate watch --once) to raise this to a top-level concern; e.g. graphile-migrate run-current or graphile-migrate watch-once or similar (suggestions welcome, I'm currently leaning towards watch-once)

Really it's "run all migrations plus the current migration and then exit"
Or "watch mode but without the watching..." 😉
-- @benjie

@dmfay
Copy link
Contributor

dmfay commented Sep 15, 2022

I was just coming here to see if this'd been suggested yet! I want to graphile-migrate a thing && pg_prove to run pgTAP tests in development.

graphile-migrate current has my vote re shorter names

@DanielFGray
Copy link

current or even latest would be my pick

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

3 participants