License file matching oversights #144353
Replies: 4 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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Workaround: ^[Ll][Ii][Cc][Ee][Nn][SsCc][Ee](?:(?:-[^.]*)?(?:\.[^.]*)?)?$ |
Beta Was this translation helpful? Give feedback.
-
The client side matching for the |
Beta Was this translation helpful? Give feedback.
-
After some experimentation, I conclude that the main issue is that no more than one dot is allowed in the filename. There also seems to be some hard to recreate unpredictable behavior when changing a license file name, maybe something to do with caching. I think the responsible piece of code needs a do-over. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
I noticed that the license file name matching isn't fully thought out and excludes some more and some less extreme edge cases. See all three branches of https://github.com/moritztim/License-Matching-Bug-Demo, particularly https://github.com/moritztim/License-Matching-Bug-Demo/tree/examples
Note
Some of the permutations aren't displayed because GitHub doesn't seem to differentiate case when the filenames are otherwise identical.
Beta Was this translation helpful? Give feedback.
All reactions