I was running github-release info from a repo, and I got this error:
{"message":"Not Found","documentation_url":"https://developer.github.com/v3/repos/#list-tags"}
I checked the repo, it resulted in user git@github.com:<username> .
However, I know that repo definitely has many releases, so something must be wrong with that username. Then I figured out that if I changed the user value to be <username>, it worked fine.
Now, the problem is that github-release commands doesn't allow --user command flag to overwrite the user value from the repo itself.
I tried github-release info --user <username>, and that ended up with the same error.
But when I modified lib/cli.js line 32 to set user value to be options.user, then it worked and I could list all the releases.
So my question is, why am I unable to use command flag --user to overwrite the user value from the repo itself? Shouldn't command line args be used to overwrite some sort of environmental defaults?
I was running
github-release infofrom a repo, and I got this error:I checked the repo, it resulted in user
git@github.com:<username>.However, I know that repo definitely has many releases, so something must be wrong with that username. Then I figured out that if I changed the user value to be
<username>, it worked fine.Now, the problem is that
github-releasecommands doesn't allow--usercommand flag to overwrite the user value from the repo itself.I tried
github-release info --user <username>, and that ended up with the same error.But when I modified
lib/cli.jsline 32 to setuservalue to beoptions.user, then it worked and I could list all the releases.So my question is, why am I unable to use command flag
--userto overwrite the user value from the repo itself? Shouldn't command line args be used to overwrite some sort of environmental defaults?