Support
Request a feature
How to suggest an improvement so that it can be weighed and built.
On this page
Ideas are collected as GitHub issues. Open a feature request. An idea that's still taking shape is welcome in Discussions first.
What makes a good request
Describe the problem before the solution.
- What are you trying to do? For example, "I want to find issues in a language I'm learning that no one has commented on."
- What happens today? What did you try, and where did it fall short?
- What would help? A sketch of the idea is welcome, but the problem matters more.
- Who else would benefit? One person's workflow and a gap many contributors hit are weighed differently.
What to check first
- Search the existing issues. If someone already asked, add your use case to that thread instead.
- Look at Finding issues. The filter or sort you want may already exist.
- Some things are known gaps, not oversights. Notifications cover only saved issues that close, there is no leaderboard yet (see Leaderboard), and there is no sponsorship yet (see Sponsor).
Things that are unlikely to be accepted
Some choices are made on purpose:
- Ranking by popularity. The default feed deliberately gives every repository one slot. Anyone who wants an order picks easiest or newest.
- Guessing difficulty. An issue with no difficulty label stays unranked.
- Anything that needs your GitHub token on our servers. The server holds none.
If your idea runs into one of these, say why you think it should change. A well-argued case can be heard.
Want to build it?
Say so on the issue. See Contribute for how to get set up.
Last updated October 21, 2026.