pingdotgg / pingdotgg/t3code

[Bug]: Azure DevOps PR comments show “most recent 0” because thread request lacks DevOps resource authentication

Open
#8,078 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce
  1. Connect T3 Code to an Azure DevOps repository containing a pull request with comments.
  2. Open the Pull Requests menu.
  3. Select a pull request that has existing comments.
  4. View the pull request details in the side panel.
  5. Check the comments section.

The panel displays “0 comments” and:

This conversation is longer than this page reads in one go. The most recent 0 are here; open it on the host to read the rest.

Adding the Azure DevOps --resource parameter to the az rest command makes the request succeed and returns the PR threads correctly. Without it, the request returns a sign-in page and T3 Code displays an empty, truncated comment list.

Expected behavior

The pull request side panel should load and display the existing Azure DevOps comments and show the correct comment count.

Actual behavior

The pull request side panel shows “0 comments” even though the pull request has comments in Azure DevOps. It also displays:

This conversation is longer than this page reads in one go. The most recent 0 are here; open it on the host to read the rest.

Impact

Minor bug or occasional failure

Version or commit

No response

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the Azure DevOps pull-request comment request in apps/desktop and find the az rest invocation used to fetch PR threads. Ensure the request includes the Azure DevOps resource parameter, then verify that a PR with existing comments shows the correct comment count and thread contents in the side panel.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.