Your first review
From an Azure DevOps organization to a reviewed pull request: sign in, connect a repository, link a work item and read the result.
This tutorial takes you from an Azure DevOps organization to your first pull request reviewed by codingassist. By the end you will have:
- created a codingassist workspace for your Azure DevOps organization
- connected one repository
- read the summary comment, the inline findings and the status check of a review
Prerequisites
| Requirement | Why |
|---|---|
| A Microsoft work or school account | Sign-in uses Microsoft Entra ID. Personal Microsoft accounts cannot sign in |
| Membership of Project Collection Administrators in the Azure DevOps organization | Only an organization administrator can create its workspace. See Roles |
| An Azure DevOps personal access token | codingassist reads repositories and posts reviews with it. See Connect Azure DevOps |
| A work item with acceptance criteria | Optional, but without it the acceptance criteria check is skipped |
Steps
Sign in
Go to app.codingassist.bot and click Continue with Azure DevOps. If your Entra tenant has not approved codingassist yet, an Approve Codingassist dialog opens. An Entra administrator approves it; if you are not one, click Copy an approval link and send it to them.
Choose the organization
Under Select an organization, pick your Azure DevOps organization and click Authorize & continue. The workspace is created on the Free plan, and you become its Owner.
Save the access token
Paste your personal access token and click Save PAT.
Connect a repository
On the Repositories page, under Available to connect, click Connect next to a repository. codingassist creates the Azure DevOps service hooks for that repository.
Open a pull request
In that repository, open a pull request and link a work item that has acceptance criteria. You can also write
AB#123in the branch name, title or description. See Work items.
Read the result
When the review finishes, the pull request has:
- a summary comment with the AC match score, the impact matrix and the findings per file. See Pull request summary
- inline comments on the lines that have findings. See Inline findings
- a status check named
PRaxiom, which fails when a Critical finding remains
Push another commit to the pull request: codingassist reviews it and updates the summary comment.
If nothing appears, see Why didn't codingassist comment on my pull request?
What just happened
codingassist read the diff, the linked work items and related code, ran static analysis, then asked a model to review the change against the acceptance criteria. The review pipeline explains each step.
Next
- The .praxiom.yml file: configure reviews per repository
- Acceptance criteria verification: how criteria are checked
- Members & invitations: add your team