Closed jombr closed 5 months ago
@djc this seems to be the right or most popular answer. Let me know if you are OK with swapping using COVERALLS_REPO_TOKEN
with the GITHUB_TOKEN
.
Otherwise, I'm not really sure why COVERALLS_REPO_TOKEN
wasn't working. I expect it should have been brought in via load_config_from_environment.
I couldn't quite verify if setting COVERALLS_REPO_TOKEN
within the shell run: |
no longer worked. So maybe doing something like...
env:
COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }}
... would still work.
...So I just defaulted to do what the coveralls-python help suggested. Figured that was the most safe path forward.
Also, let me know if you do or don't want me to bug you with reviews.
Getting the following error
Running on Github Actions but GITHUB_TOKEN is not set. Add "env: GITHUB_TOEKN: ${{ secrets.GITHUB_TOKEN }}" to your step config.
Following directions from latest coveralls python (3.3.1) help for Github Actions https://coveralls-python.readthedocs.io/en/latest/usage/configuration.html#github-actions-support