Well, you could throw in something like this - https://github.com/nicobrenner/commandjobs/compare/master...BenQuigley:commandjobs:master https://github.com/nico

Well, you could throw in something like this - https://github.com/nicobrenner/commandjobs/compare/master...BenQuigley:commandjobs:master https://github.com/nicobrenner/commandjobs/compare/master...... You can also go further by writing code that prompts the user for these values, one by one, and stores them in a config file. But for a CLI application, you might reasonably wonder if the juice is worth the squeeze there. CLI users tend to be comfortable editing a config file to hold a secret. Edit: or if some of those values are actually optional, then you would maybe exclude them from this check.