write_repository Grants read-write access to repositories on private projects using Git-over-HTTP (not using the API). ( Introduced in GitLab 12.10.) read_repository Grants read-only access to repositories on private projects using Git-over-HTTP or the Repository Files API. read_api Grants read access to the API, including all groups and projects, the container registry, and the package registry. Also grants access to read-only API endpoints under /users.

read_user Grants read-only access to the authenticated user’s profile through the /user API endpoint, which includes username, public email, and full name. Scope Access api Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry. Personal access tokens no longer being able to access container or package registries introduced in GitLab 16.0.Ī personal access token can perform actions based on the assigned scopes. To do this, you can append a name parameter and a list of comma-separated scopes You can link directly to the Personal Access Token page and have the form prefilled with a name and Prefill personal access token name and scopes Save the personal access token somewhere safe. By default, this date can be a maximum of 365 days later than the current date.If you do not enter an expiry date, the expiry date is automatically set to 365 days later than the current date.The token expires on that date at midnight UTC.Enter a name and expiry date for the token.On the left sidebar, select Access Tokens.

In the upper-right corner, select your avatar.You can create as many personal access tokens as you like. Ability to create non-expiring personal access tokens removed in GitLab 16.0.Introduced in GitLab 15.3, default expiration of 30 days is populated in the UI.

Download webstorm trial license