[BUG]: Confusing PAT requirements

[jovere]

Creating a PAT is confusing. The documentation shows the software flags for the PAT, yet when trying to create a PAT through the web interface as specified, it gives user-friendly descriptions that don't match. A decent amount of sleuthing needs to occur to determine which boxes need to be checked. Please change the documentation to be more user friendly.

See below for comparison:

This is the Documentation

This is what I see in Azure Devops:

[Jonatha1983]

@jovere Thanks for reporting

You are completely right, I will fix the documentation.

Thanks for reporting

[Jonatha1983]

I wish there was an end point like in gitlab and GitHub to open the Pat creation page already set with the requested token - but unfortunately there isn't.

[Jonatha1983]

Just to be clear those token in value I wrote in the documentation were taken from Azure Devops rest api documentation.

I just saved a list of those during development based on the call the plugin is making and that is the current list, but again I will update the docs.

[jovere]

I'm a bit confused as to why I need to manually create a PAT in the first place. When I use CLion to do Git actions, it pops up a browser page for me to log in and then a PAT is automatically created without any other interaction.

[Jonatha1983]

@jovere You need the PAT because the plugin is doing REST api calls for you in order to get the pull request and pipelines information so you can interact from within the IDE.

Those are not git cli command as the default CLion is doing.

[Jonatha1983]

@jovere hi

Here is a link to the updated documentation about the scopes.

Thanks for reporting.

[jovere]

Excellent, thanks!