[Bug]: Azure DevOps PR icon is technically wrong
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- azure, typescript
- Domain
- desktop
Research direction
Start in apps/desktop by locating the “View PR” button and the code path that renders its icon for Azure DevOps pull requests. Replace the Azure icon selection with the Azure DevOps icon and verify that Azure DevOps PRs show the correct icon without changing other providers.
Written by the indexing model from the issue text.
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
- Have a PR open for a branch on Azure DevOps and open it within T3 Code.
- Look at the "View PR" button icon
Expected behavior
I'd expect that to be the Azure DevOps icon:
Actual behavior
"View PR" button for an Azure DevOps PR shows the Azure icon, not the Azure DevOps icon.
Impact
Cosmetic issue
Version or commit
No response
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
- Dominant language
- TypeScript
- Stars
- 23.6k
- Forks
- 6.1k
- Avg merge
- 8h 51m
- Merged PRs (30d)
- 350
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pingdotgg/t3code#14066 · 1 comment ·
Maintainers usually reply within 1 day
-
bug upstream via-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
pingdotgg/t3code#13990 · 1 comment ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
pingdotgg/t3code#13977 · 1 comment ·
Maintainers usually reply within 1 day
-
needs more info via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pingdotgg/t3code#13851 · 3 comments ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
pingdotgg/t3code#13831 · 1 comment ·
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mermaid-js/mermaid-live-editor#2053 ·
Maintainers usually reply within 1 day
-
factory
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jessepollak/home#1455 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
lingdojo/kana-dojo#31227 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
appandflow/stim#1838 ·
Maintainers usually reply within 1 day