You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Azure DevOps: post comments, line comments and replies from the PR review pane
#18722
Azure DevOps pull requests are read-only in T3 Code. The review pane shows their conversation but hides the composer, and the provider refuses comment, line comment, reply and resolve with "Azure DevOps reviews cannot be written from here yet."
#4849 left these writes out for two reasons. Azure had no patch to write line comments against, and nobody had credentials to test them. #7721 has since built a diff from iteration changes, so the first reason is gone. I use Azure DevOps at work and have a working implementation, tested end to end against a real Azure DevOps organization.
Proposed scope, one PR, all in source-control-azure-devops:
Post a PR-level comment from the composer.
Post line comments through the existing review flow, using only the "comment" verdict. No votes.
Reply to a line thread, and resolve or reopen it.
Read Azure's file-anchored threads as review threads, tracked to the latest iteration, so they show on the right lines in the Code tab. Today they only show in the timeline.
Everything goes through the threads REST API via az devops invoke, the same transport the provider already reads threads with. Request bodies go through a temp file (--in-file), not argv (so it works on Windows too).
Out of scope, possible follow-ups: editing comments and approve/reject votes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Azure DevOps pull requests are read-only in T3 Code. The review pane shows their conversation but hides the composer, and the provider refuses comment, line comment, reply and resolve with "Azure DevOps reviews cannot be written from here yet."
#4849 left these writes out for two reasons. Azure had no patch to write line comments against, and nobody had credentials to test them. #7721 has since built a diff from iteration changes, so the first reason is gone. I use Azure DevOps at work and have a working implementation, tested end to end against a real Azure DevOps organization.
Proposed scope, one PR, all in
source-control-azure-devops:Everything goes through the threads REST API via
az devops invoke, the same transport the provider already reads threads with. Request bodies go through a temp file (--in-file), not argv (so it works on Windows too).Out of scope, possible follow-ups: editing comments and approve/reject votes.
Would you accept a PR with this scope?
All reactions