Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coveralls: use Coveralls specific token #227

Merged
merged 1 commit into from
May 3, 2023

Commits on May 3, 2023

  1. Coveralls: use Coveralls specific token

    Coveralls prefers for repos to be identified with the Coveralls specific token they provide. While the GitHub secret token still works, the intention is to drop support for it at some point in the future.
    
    This commit anticipates on that by switching the token.
    
    Notes:
    * The `COVERALLS_TOKEN` has been added to the repo secrets.
    * People with admin access to the GH repo automatically also have access to the admin settings in Coveralls.
        If ever needed, the Coveralls token can be found (and regenerated) in the Coveralls admin for a repo.
    * After regeneration, the token as stored in the GH repo Settings -> Secrets and Variables -> Actions -> Repository secrets should be updated.
    
    :point_right: This does mean that forks which have turned Coveralls on for their own fork of this repo will also need to add a `COVERALLS_TOKEN` secret to their GitHub fork (with the token as can be found in the Coveralls settings for their fork).
    This is a one-time only action.
    jrfnl committed May 3, 2023
    Configuration menu
    Copy the full SHA
    7072b38 View commit details
    Browse the repository at this point in the history