Authentication failure with valid token

[Arcanemagus]

Current behavior

semantic-release is throwing an EGITNOPERMISSION error, even though the same token works perfectly when manually running the command that supposedly is failing.

Expected behavior

When a GITHUB_TOKEN is provided with the proper credentials, it should work.

Environment

• semantic-release version: ^15.1.7 (15.2.0 tested)
• CI environment: Travis CI
• Plugins used: No extra plugins
• semantic-release configuration: @semantic-release/apm-config@^2.0.1
• CI logs:
  • Failing deploy
  • Passing manual test of command

Additional Information

Potentially related to the changes to fix #709?

[pvdlg]

I looked in detail but I couldn't figure out what happened...

I don't think it could be related to #709 as I don't see the message The local branch %s is behind the remote one, therefore a new version won't be published in the logs.

I opened #772 that logs the output of the git push --dry-run. That would help debugging hopefully.

What happen if you set the DEBUG environment variable to semantic-release:* in Travis and restart the hob https://travis-ci.org/AtomLinter/linter-htmllint/jobs/373647402 ?

[Arcanemagus]

Ah ha! It looks like the repository definition wasn't quite correct, leading it to not recognize the repository!

[pvdlg]

That's weird, the URL seems correct. But it seems the git CLI doesn't like it...

[pvdlg]

I think we had cases where adding .git at the end of the URL solved this type of issue.
It might be related to the git version. On my local machine with version 2.17.0, it works with and without the trailing .git. It seems that on Travis it might make a difference.

[Arcanemagus]

Yea, I've had to add .git on the end of all the repos so far. This is one of the 2 that I haven't done personally and I forgot to check it myself.

[pvdlg]

I'm really curious to know why the trailing .git makes a difference in some cases.
I tested there https://travis-ci.org/pvdlg/test-sr/jobs/374590162#L443 and it seems both works.

Maybe an obscure thing with slightly different version of git running on different Travis images....

[Arcanemagus]

Your test job is running on the node_js image just like these builds, so it's not the image itself at least.

[pvdlg]

Indeed. Can't figure out what's causing this "not found" error when omitting the .git...

[Arcanemagus]

Confirming that adding it at least fixed the build.

[pvdlg]

Great news!
I'd like to figure out when exactly the .git is required as some people have encounter this issue as well... If anyone reading this thread has any idea...

[pvdlg]

Closing in favor of #774