Docs feedback - feature proposal: Add write_registry scope to personal access token (similar to deploy token)

Problem to solve

Pushing to docker registry using a personal access token requires at least api scope. In some cases write_registry is more restricted and more appropriate. Alternative is to use a group deploy token but means moving a set of projects to a group. This is often inconvenient. The problem is exacerbated with docker where only one login can be made per registry. This means project deploy tokens can not easily be used.

Intended users

User experience goal

Proposal

Add write_registry scope to personal access token (similar to deploy token)

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

Ability to push to docker without any other write access to gitlab for a particular user and personal access token.

What is the type of buyer?

Is this a cross-stage feature?

Links / references