We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Seems like #41 broke GitHub's parsing of the repo license. According to https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository they want a file named "LICENSE or LICENSE.md (with all caps)".
LICENSE
LICENSE.md
The README.md already contains a "license" section, but no SPDX id. The Cargo.toml also includes a license field.
README.md
Cargo.toml
license
Apart from GitHub maybe some research can gather expectations from other tools, e.g. a LICENSE.spdx file seems to be used elsewhere.
LICENSE.spdx
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Seems like #41 broke GitHub's parsing of the repo license.
According to https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository they want a file named "
LICENSE
orLICENSE.md
(with all caps)".The
README.md
already contains a "license" section, but no SPDX id.The
Cargo.toml
also includes alicense
field.Apart from GitHub maybe some research can gather expectations from other tools, e.g. a
LICENSE.spdx
file seems to be used elsewhere.The text was updated successfully, but these errors were encountered: