continuous-integration.yml: use COVERALLS_TOKEN to send coveralls rep… #3433
Conversation
…orts This is how it is documented in https://github.com/nickmerwin/node-coveralls#usage I dont know why this worked before. For php we use the github action, and there we only need this special token for sending local coverage info to coveralls: https://github.com/marketplace/actions/coveralls-github-action For the github action, the GITHUB_ACTION token suffices.
|
What is a little scary is that npx coveralls worked on my fork without a coveralls token: https://github.com/BacLuc/ecamp3/actions/runs/4849643951/jobs/8641827192 |
|
coveralls seems to work again...? |
|
Check this comment: lemurheavy/coveralls-public#1607 (comment) It seems there is some special logic on coveralls side. When COVERALLS_SERVICE_NAME equals github, coveralls would accept GITHUB_TOKEN. The official documentation suggests however, that in this case, the github token should be passed via environment variable GITHUB_TOKEN. So the behaviour that the github token is accepted in COVERALLS_REPO_TOKEN seems not a officially documented method. I think the safest way is to use a different COVERALLS_SERVICE_NAME for frontend and print. |
|
Will close that for now |
…orts
This is how it is documented in https://github.com/nickmerwin/node-coveralls#usage I dont know why this worked before.
For php we use the github action, and there we only need this special token for sending local coverage info to coveralls: https://github.com/marketplace/actions/coveralls-github-action For the github action, the GITHUB_ACTION token suffices.