anuraghazra
Top Issues Dashboard
A simple dashboard that lists the top issues/bugs/features and pull requests.
Top issues
- #1 :+1:
287 - #1471 :+1:
114 - #4658 :+1:
71 - #4666 :+1:
50 - #654 :+1:
20 - #2282 :+1:
19 - #2603 :+1:
17 - #1406 :+1:
14 - #4665 :+1:
13 - #2179 :+1:
12
Top bugs
- #4658 :+1:
71 - #4666 :+1:
50 - #2603 :+1:
17 - #4665 :+1:
13 - #4680 :+1:
10 - #4641 :+1:
10 - #3850 :+1:
10 - #1801 :+1:
9 - #4687 :+1:
8 - #4681 :+1:
7
Top feature requests
- #1 :+1:
287 - #654 :+1:
20 - #2282 :+1:
19 - #2179 :+1:
12 - #1761 :+1:
11 - #1437 :+1:
10 - #4241 :+1:
8 - #1633 :+1:
7 - #3767 :+1:
5 - #1247 :+1:
4
Top PRs
- #1122 :+1:
20 - #1653 :+1:
8 - #1202 :+1:
6 - #2409 :+1:
5 - #4645 :+1:
4 - #4026 :+1:
4 - #3312 :+1:
4 - #3182 :+1:
4 - #2537 :+1:
4 - #4371 :+1:
2
Created by the rickstaa/top-issues-action action (last update: 12/10/2025, 12:36:53 AM).
@rickstaa can I be assigned this?
Hey, @arndom! No, you can't be assigned. This is special automatically generated dashboard issue for tracking community demand. It should be never closed or assigned to someone for any reason. You can choose some issue that you are interested in working on from the list.
Oh ok, my bad. Maybe a label could be added to indicate that ?
This issue already has a special unique label "top issues dashboard".
https://github.com/anuraghazra/github-readme-stats/labels/%3Astar%3A%20top%20issues%20dashboard
Ooh, didn't realize that, thanks.
On Tue, 10 Oct 2023, 05:12 Alexandr Garbuzov, @.***> wrote:
Oh ok, my bad. Maybe a label could be added to indicate that ?
This issue already has a special unique label "top issues dashboard".
— Reply to this email directly, view it on GitHub https://github.com/anuraghazra/github-readme-stats/issues/1935#issuecomment-1754323689, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJVPQPSSW57I2AVQYMXDHOTX6TDLVAVCNFSM56DMMUE2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZVGQZTEMZWHA4Q . You are receiving this because you were mentioned.Message ID: @.***>
Hello @rickstaa, I'm a maintainer over at spectre.console. Limited maintainer capacity means we've been looking at ways to manage the volume of incoming issues/PRs. Your dashboard above looks most suitable. I don't (currently) know anything about github actions bots, but I'm wondering if it's something that could be copied to our repo.
Update - I've just seen your repo: https://github.com/rickstaa/top-issues-action
Hello @rickstaa, I'm a maintainer over at spectre.console. Limited maintainer capacity means we've been looking at ways to manage the volume of incoming issues/PRs. Your dashboard above looks most suitable. I don't (currently) know anything about github actions bots, but I'm wondering if it's something that could be copied to our repo.
Update - I've just seen your repo: https://github.com/rickstaa/top-issues-action
Hey @FrankRay78, it's fantastic to hear that you like my action and are considering it for https://github.com/spectreconsole/spectre.console 🚀. The action targets open-source projects like GRS that don't have a clear backlog or development pipeline. If you have any questions or feature requests, don't hesitate to ask 🙂.
Hello @rickstaa, I'm a maintainer over at spectre.console. Limited maintainer capacity means we've been looking at ways to manage the volume of incoming issues/PRs. Your dashboard above looks most suitable. I don't (currently) know anything about github actions bots, but I'm wondering if it's something that could be copied to our repo.
Update - I've just seen your repo: https://github.com/rickstaa/top-issues-action
Hey, @FrankRay78. In order to copy this to your repository you have to create .yml file in .github/workflows with the following content https://github.com/anuraghazra/github-readme-stats/blob/master/.github/workflows/top-issues-dashboard.yml with optional changing of inputs depending on your needs. If you need any help feel free to contact @rickstaa or me.
Thanks, I've got it setup on one of my test repos and it's working excellently. I'll submit a PR to spectre.console this week for the same. We are in a similar situation re low maintainer capacity, so priority based roadmap planning seems ideal. Really great work.
🌚:-)(^^)(TT)(*)(+_+)\0/*Oo(✷‿✷)<(￣︶￣)>( ꈍᴗꈍ)(◕ᴗ◕✿)
