[en] Fine-grained personal access tokens (PATs) give you more control over how the Acrolinx for Git Hosting integration interacts with your Git repositories. For example, you can use them to grant access to a specific set of repositories. Learn more about fine-grained PATs in the GitHub documentation.
[en] To use fine-grained PATs with Acrolinx for Git Hosting, the following repository permissions are required at a minimum:
|
[en] Repository Permission |
[en] Scope |
[en] Purpose |
|---|---|---|
|
[en] Webhooks |
[en] Read and write |
[en] Enables installation of a webhook via the Acrolinx integration. For more information, visit Install, Uninstall, or Update Acrolinx for GitHub. |
|
[en] Issues |
[en] Read and write |
[en] Lets Acrolinx create issue comments in pull requests. |
|
[en] Commit Statuses |
[en] Read and write |
[en] Marks a pull request as |
|
[en] Contents |
[en] Read and write |
[en] When initiated in Baseline mode, the integration also posts a quality snapshot of your repositories to the repository folder that you’ve specified via the |
|
[en] Pull Requests |
[en] Read and write |
[en] Allows Acrolinx to read the changed files in a pull request and post comments and status updates to it. |
[en] If you want to grant access to a specific repository, make sure to include access to the repository specified under :data-repo-content-url. This is the location of the global remote configuration and the repository registry.
Hinweis
[en] Each fine-grained PAT can only access resources owned by a single user or organization. If you need access to repositories owned by an organization, the use of fine-grained PATs needs to be enabled at an organizational level.