Skip to content
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

Update LICENSE file #1105

Merged
merged 1 commit into from
Apr 12, 2023
Merged

Update LICENSE file #1105

merged 1 commit into from
Apr 12, 2023

Conversation

martincostello
Copy link
Member

Use a LICENSE file that matches the conventions tools expect to find when analysing a repository.

The license itself isn't being changed, just the location in the repo and the boilerplate is copied from that made for a new repo in GitHub.com when BSD 3-Clause "New" or "Revised" License is chosen in the UI (example).

I found this as part of #1104 as the OpenSSF Best Practices tooling didn't parse the license and treated it as "OTHER". Similarly, the repo's current license file doesn't show a GitHub banner with license information either.

Use a LICENSE file that matches the conventions tools expect to find when analysing a repository.
The license itself isn't being changed, just the location in the repo and the boilerplate is copied from that made for a new repo in GitHub.com when `BSD 3-Clause "New" or "Revised" License` is chosen in the UI.
@joelhulen joelhulen merged commit a058852 into App-vNext:main Apr 12, 2023
@martincostello martincostello deleted the fix-LICENSE branch April 12, 2023 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants