Replies: 2 comments
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
BetaWas this translation helpful?Give feedback.
-
You're right — Right now there’s no built-in way to enforce “root only”, but two partial workarounds help:
This limitation is known and has been requested, but isn’t supported yet. |
BetaWas this translation helpful?Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
Output from copilot says it all :-(
"It is pretty rough, honestly. For a platform that hosts the world’s code, GitHub’s search engine has some surprising blind spots — and the “root‑level LICENSE” issue is one of the biggest.
GitHub parses licenses, but it does not let you:
filter by directory depth
require a file to be in the root
exclude monorepo subfolders reliably
distinguish between inherited license metadata and actual files
So even though developers expect precise filtering, GitHub’s search behaves more like a fuzzy index than a strict file‑system query.
And you’re not alone — this exact complaint shows up constantly in GitHub Issues, StackOverflow threads, and dev forums. GitHub simply hasn’t added the feature."
BetaWas this translation helpful?Give feedback.
All reactions