Skip to content

docs: correct documentation about long lived personal access tokens #394

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 17, 2024
Merged

docs: correct documentation about long lived personal access tokens #394

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions frontend/docs/api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,8 +214,11 @@ JSR supports authenticating with three types of tokens:

- Long-lived personal access tokens, which are used to authenticate as a user.
Personal access tokens may have an expiration date, and may grant only limited
permissions. Personal access tokens are created by the user in their account
settings page.
permissions.

> A user will be able to create personal access tokens in the user in their
> account settings page. This is not yet implemented. See
> [issue #393](https://github.com/jsr-io/jsr/issues/393).

- GitHub Actions OIDC tokens, which are used to authenticate as a GitHub Actions
runner. These tokens are created from within GitHub Actions, and are only
Expand Down