Skip to content

Commit

Permalink
docs: recommend regenerating JWT tokens at every release
Browse files Browse the repository at this point in the history
Signed-off-by: Leonardo Di Donato <[email protected]>
  • Loading branch information
leodido committed Sep 25, 2024
1 parent 23f8c2d commit bb873b1
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,9 +66,12 @@ Because of the `ci` option set to `true`, it will also start the CI eavesdrop to

Notice it only works on linux runners.

Where to get your JWT token?
**Where to get your JWT token?**

[How to get your API key from the project settings](https://docs.listen.dev/workflows/generate-api-token).

It's _recommended_ to regenerate the JWT token for every release, until we will release stable versions.

[Get your API key from the project settings](https://docs.listen.dev/workflows/generate-api-token)
<details>
<summary>Do you also want to also use another reporter together with the pro one?</summary>

Expand Down

0 comments on commit bb873b1

Please sign in to comment.