Disability accomodations request (filter GitHub search results of repos by number of lines of code in the repo)

[JohnReedLOL]

I just read the post on the front page of GitHub's blog about the Global Accessibility Awareness Day (GAAD) pledge. This:
https://github.blog/open-source/social-impact/our-pledge-to-help-improve-the-accessibility-of-open-source-software-at-scale/

I have a mental disability where I lack spatial navigation. Like despite being 31, I have never been able to go more than about a couple miles away from my residence without getting lost and needing to rely on Google Maps for navigation. I can't navigate out of an American corn maze without help (in a reasonable amount of time).

Anyway, this disability makes large codebases, repositories with many lines of code in them, insurmountable for me. In order to find a worthwhile project on GitHub that I can navigate, understand, and effectively contribute to, I need to be able to filter the GitHub search results of repos by the number of lines of code in the repo. For example, I need to be able to make a GitHub search that is like:

"type=Repositories AND stars>1000 AND codeLines<20000"

👆 That may not be the exact right syntax, but you get the idea. Like I need to be able to make a GitHub search that is like "Give me all repos with more than 1000 stars and less than 20000 lines of code".

As a means of improving accessibility for people with disabilities, can GitHub implement this search feature? I would like to see it added to the options in GitHub advanced search, this:
https://github.com/search/advanced

p.s. I tried to use the "Repositories of this size in KB" option in GitHub advanced search as a sort of substitute or approximation for the number of lines of code in the repo, but it was a very, very poor approximation. I could not use it as a substitute. It might be possible to use something other than the exact number of lines of code in the repo as a search parameter for this purpose, maybe something related that is strongly correlated with the number of lines of code in a repo, but the existing search options are insufficient.

Edit 1: I wasn't 100% sure where the right place to place this feature request is, so I also put it here:
https://github.com/orgs/community/discussions/159410 . Oh, it's closed there now.

Edit 2: Oh, also, in addition to being able to filter the GitHub search of repositories by number of lines of code in the repository, I would also like to be able to do that same sort of a filter on issues that are attached to a repository. Like I need to be able to make a GitHub search that is like "Give me all open issues with the 'bug' label where the repo that has the issue has less than 20000 lines of code in it". Something sort of like this:

"type=Issues AND state=open AND label=bug AND repoCodeLines<20000"

The goal is to find GitHub issues in small codebases that are easy for me to navigate, understand, and learn. Fixing an issue in a massive, complex codebase on my own is impossible for me, I need the issue to be in a small codebase.

[ghost]

That's an interesting point about how the structure of repositories can be challenging to navigate. Filtering by the number of lines of code sounds like a very useful feature, not just for accessibility but potentially for anyone trying to find projects of a specific scope. I hope GitHub takes this suggestion into consideration for the advanced search options.

[JohnReedLOL]

There's a history of disability accomodations helping non-disabled people too, like requiring Closed Captions (CC) on US television so deaf people can watch it resulted in the US literacy rate going up because people read what was being said on TV.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ghost]

This accessibility concern is likely the most important part of this thread. A disabled person is requesting a specific feature meant for disabled people.

…

On Fri, May 16, 2025, 2:32 AM John Michael Reed ***@***.***> wrote: There's a history of disability accomodations helping non-disabled people too, like requiring Closed Captions (CC) on US television so deaf people can watch it resulted in the US literacy rate going up because people read what was being said on TV. — Reply to this email directly, view it on GitHub <#159406 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXBAKHVBENC7HDJSII3BUDD26WWB5AVCNFSM6AAAAAB5HQE236VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJWHA3TEMI> . You are receiving this because you commented.Message ID: ***@***.***>

[ghost]

@JohnReedLOL This is an important request, and with the Accessibility label already in place, it clearly highlights a need for GitHub to be more inclusive. Framing this consistently as an accessibility feature – one that removes barriers for users with disabilities – can be a powerful way to advocate for its implementation. This approach aligns with broader efforts to ensure digital platforms are usable by everyone and can resonate with GitHub's commitment to accessibility. By focusing on the removal of barriers and the creation of a more inclusive platform, we can collectively emphasize the importance of this feature for the entire community.