Repository permission issues
Fix the Azure DevOps access token, the service hooks of a repository, and rejected webhook deliveries.
When a connected repository gets no reviews, or reviews that are never posted, the cause is usually the access token or the service hooks.
The access token
codingassist calls Azure DevOps with the organization's personal access token (PAT). The token must let codingassist:
- read code, pull requests and work items
- post comments and statuses on pull requests
- create service hooks, when a repository is connected
The token screen in the web app mentions read access on Code and Project only. Posting comments and statuses also needs write access: a read-only token lets codingassist read the pull request but not post the review.
To show the members of the Azure DevOps organization on the Members & roles page, the token also needs read access to member entitlements or to the Graph.
When the token expires or is revoked in Azure DevOps, reviews cannot be read or posted. Replace it under Organization > Access tokens: see Replace the token.
The service hooks
Each connected repository has three service hooks in Azure DevOps: pull request created, pull request updated and pull request commented on. You can see them in the project's Project settings > Service hooks.
If a hook was deleted or disabled, or its deliveries fail with 401 Unauthorized, disconnect the repository on the Repositories page and connect it again. This recreates the three hooks.
GitHub
GitHub is not available in the web app yet. codingassist connects to Azure DevOps today.