Incorrect Usage Display in GitHub Copilot
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github
- Domain
- desktop
Research direction
Start with the code that loads and displays GitHub Copilot budget or usage metrics in app version 1.1.30. Reproduce by increasing the budget manually and checking whether the displayed status and usage data refresh with the updated value. Done means the interface shows an accurate breakdown consistent with the new budget rather than only indicating that the plan is full.
Written by the indexing model from the issue text.
Description
I'm encountering an issue with GitHub Copilot where my usage metrics aren't displaying correctly. When I manually increase my budget, it doesn't reflect the increase in my usage metrics.
This lack of accurate information makes it challenging to determine when I need to adjust my budget. Instead of receiving a clear breakdown of my usage, I only see that my plan is full, which leaves me with 0 status regarding my budget usage. Check the image below.
Steps to Reproduce:
- Access GitHub Copilot.
- Manually increase the budget.
- Check the usage metrics.
| Field | Value |
|---|---|
| App version | 1.1.30 |
| OS | Windows 10.0.26300 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 3 |
- Dominant language
- No language data
- Stars
- 2.2k
- Forks
- 183
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 github/app
-
https://docs.Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Similar issues
-
Locked plugin flip-flops position on every refresh after being disabledPossibly taken @Illustar0 claimed this today. Openissue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ModOrganizer2/modorganizer#2449 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bitwarden/clients#24012 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug module: omni
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chthollyphile/folia-major#812 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day