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
Currently, an option expected from the user is not usually consistent with the corresponding option hash key. For instance, --enhancement-label [LABEL] is stored as options[:enhancement_prefix] (_label part is stored as _prefix internally). This produces incompatibility with the parser_file.rb code.
That is why, there appear a situations similar to the following. One tries to use GitHub Enterprise, and provides the following entries in his .github_changelog_generator:
Then, while invoking the binary, he receives the following error:
Bad credentials.
Error: wrong GitHub token
Since parser_file.rb placed github-api configuration entry as :github_api key in the hash, while :github_endpoint was expected. Then Github.new is being invoked as
which actually causes the error above. And that was not very straightforward to troubleshoot.
Do you think that is wise to add some additional conditionals/logics into parser_file.rb to deal with such non-conformant options? I might be able to take this on.
Currently, an option expected from the user is not usually consistent with the corresponding option hash key. For instance,
--enhancement-label [LABEL]
is stored asoptions[:enhancement_prefix]
(_label
part is stored as_prefix
internally). This produces incompatibility with theparser_file.rb
code.That is why, there appear a situations similar to the following. One tries to use GitHub Enterprise, and provides the following entries in his
.github_changelog_generator
:Then, while invoking the binary, he receives the following error:
Since
parser_file.rb
placedgithub-api
configuration entry as:github_api
key in the hash, while:github_endpoint
was expected. ThenGithub.new
is being invoked aswhich actually causes the error above. And that was not very straightforward to troubleshoot.
Do you think that is wise to add some additional conditionals/logics into
parser_file.rb
to deal with such non-conformant options? I might be able to take this on./CC: @dlanileonardo
The text was updated successfully, but these errors were encountered: