Error: HttpError: Bad credentials
See original GitHub issueGetting an error of Error: HttpError: Bad credentials
,
All the tests are run successfully, but I get an error when trying to publish the report. Is there anything wrong with my GitHub token, does it require any specific permission to publish the report?
Here is my runner file
pull-request-coverage.yml
name: Get Test Coverage
on:
pull_request:
branches:
- main
jobs:
coverage:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Install dependencies
run: yarn install
- name: Get Coverage
uses: ArtiomTr/jest-coverage-report-action@v2.0-rc.6
with:
github-token: ${{ secrets.PERSONAL_GITHUB_TOKEN }}
package-manager: yarn
test-script: yarn test:ci
threshold: 60
Runner failed
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Bad credentials] personal token auth to create a gist doesn't ...
What happened? I'm running this, following the create a gist section. const octokit = new Octokit({ auth: token }); await ...
Read more >GitHub API 401 Bad Credentials in Node but not curl
can anybody advise why it doesn't? This is the full HTTP response I get: { HttpError: {"message":"Bad credentials" ...
Read more >When a login is failed due to the wrong credentials ... - Quora
The error code for wrong credentials is 401 which indicates that the credentials are missing or are wrong. 403 Forbidden indicates that the...
Read more >Troubleshooting GitHub tokens - RStudio Community
Using github PAT from envvar GITHUB_PAT Error: Failed to install 'unknown package' from GitHub: HTTP error 401. Bad credentials Rate limit ...
Read more >Bad Credentials: The Email Server is Saying Exactly What it ...
We have yet to encounter a case other than this meaning exactly what is says. It's a bad username/password error returned from email...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kevalsavani,
I see now, that you’re using two different workflows - one for testing and one for publishing. So, because you have different workflows, you can use two different tokens - just pass GITHUB_TOKEN for jest-coverage-report-action, and use PERSONAL_GITHUB_TOKEN for your publishing workflow.
Regarding NODE_AUTH_TOKEN - this token should be from the registry, to which you’re publishing. You’ve set up
https://npm.pkg.github.com/
. This means, that you will publish to the GitHub package registry, so the token should be from there.Hi, @ArtiomTr yes, I was expecting the same thing, thank you for clarification 🎉, closing the issue 🎉