Config File

[jpchip]

There are starting to be a lot of options, which are hard to enter via cli, and annoying to maintain as both cli and .env file options. Refactor app to run off a json config file instead, which would have all available options inside it.

1. add an init command, like gg init which would generate the config file (ie. ggrc.json)
2. Running gg without config file will ask you to run gg init first
3. Drop support for env variables and force everything to be in the single config file. Leave --page support.

Can do this all using the yargs library that's already part of the code base. Would be extra cool though if gg init prompted you for credentials and stuff, using Inquirer.js.

This would be a HUGE breaking change and would have to be a major release.

Not sure if I'll have the time to go through with this, but wanted to write it down while I was thinking about it.

[famewolf]

Does your gg init import information from the .env to populate the config file? I could easily write a shell script to convert a .env into a config file since all the information is already there but that wouldn't work for the windows users. I ask because I just built my config file manually copying info from my .env so don't know how it works.

[jpchip]

Nope, it does not. I thought about it, but it seemed like way too much effort for me, so I put that effort on the user instead. :p But running gg init would have walked you step by step through entering the values for the config file. What you did wasn't much harder though.