Hi@mcelicalderon! Thanks for your contribution. Would you mind adding a test case?

Thanks!

Sure, I'll get to this as soon as possible. In fact, what would you think about having a constant with all the options available so both the task and binary can use them. That way both will always support the same options.
Maybe something like this, but would still have to look at other parts of the code:

AVAILABLE_OPTIONS={user:{short:'-u',long:'--user USER',description:'Username of the owner of target GitHub repo.'},project:{ ...},token:{ ...}}.freeze

and then on the rake task we could just do

AVAILABLE_OPTIONS.keys.eachdo

and the parser would just use the hash to define options.