-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add REUSE support in the GitHub licensee library #901
Comments
licensee/licensee#635 looks like a related issue on their side although it's only about SPDX identifiers rather than the LICENSES/ directory. |
There have been a number of upstream issues about this already, and also discussions via Twitter IIRC. Mike Linksvayer has made it quite clear that they only implement this when a pull request is made by a third party. The REUSE team doesn't currently plan to do that but we welcome any initiative! |
The PR should target which repo? |
Indeed, unless GitHub has changes libraries in the mean time, but I wouldn't think so. Regardless, it would be good to have it in this commonly used library. |
Linking the relevant licensee issue here: licensee/licensee#490 |
Currently it seems that the GitHub licensee Ruby library they use for detecting licenses does not read the path
LICENSES/
. People hosting their code on GitHub probably value having GitHub detect their license correctly. Thus it might help drive adoption if the licensee matchers at https://github.com/licensee/licensee/tree/main/lib/licensee/matchers were extended to read the places REUSE recommends developers to use.I am posting this for visibility while I am fully aware that this is not a bug in the reuse-tool itself.
The text was updated successfully, but these errors were encountered: