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鈥檒l 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

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented May 3, 2023

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.

馃憠 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.

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 jrfnl added this to the 1.0.4 milestone May 3, 2023
@jrfnl jrfnl merged commit b62cdf0 into develop May 3, 2023
35 checks passed
@jrfnl jrfnl deleted the feature/ghactions-use-coveralls-token branch May 3, 2023 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant