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
{{ message }}
This repository was archived by the owner on Mar 14, 2023. It is now read-only.
Making this issue here to brainstorm the best way to handle this.
Here's what I'm currently thinking:
Allow setting a "default" environment statically in shipit.initConfig.
Environment set in the CLI command would override.
This would allow for workflows where certain branches deploy to certain environments by default (e.g. master → production, development → development). The user could set the environment in shipit.initConfig to a function that parsed your current git branch and returned the matching environement. Of course, they could always override it by passing an environment in the CLI
If no environment set in either CLI or shipit.initConfig, trigger an inquirerchoices prompt.