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

The repo license doesn't get recognized by GitHub again #56697

Closed
MichaelAgarkov opened this issue Aug 1, 2021 · 5 comments
Closed

The repo license doesn't get recognized by GitHub again #56697

MichaelAgarkov opened this issue Aug 1, 2021 · 5 comments
Labels
area-Infrastructure untriaged New issue has not been triaged by the area owner

Comments

@MichaelAgarkov
Copy link

image

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Aug 1, 2021
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@hez2010
Copy link
Contributor

hez2010 commented Aug 1, 2021

Need revert #37626. But it requires arcade being updated first so that the license can be recognized by build toolchain.

@msftbot
Copy link
Contributor

msftbot bot commented Aug 6, 2021

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

image

Author: MichaelAgarkov
Assignees: -
Labels:

area-Infrastructure, untriaged

Milestone: -

@msftbot msftbot bot added this to Untriaged in Infrastructure Backlog Aug 6, 2021
@krwq
Copy link
Member

krwq commented Aug 6, 2021

changing area label since the suggestion is that Arcade should be updated

@krwq krwq removed this from Needs triage in Triage POD for Meta, Reflection, etc Aug 6, 2021
@ViktorHofer
Copy link
Member

ViktorHofer commented Aug 6, 2021

The repo license doesn't get recognized by GitHub again

The repo license never got recognizhed by GitHub for dotnet/runtime as the THIRD-PARTY-NOTICES.TXT lists conflicting licenses which confuses GitHub's license detection. There is nothing that we can do that and likely need support from GitHub to exclude files from their license detection logic. More information can be found here: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository.

Closing as not actionable. Feel free to reopen if you disagree or if I'm mistaken.

Infrastructure Backlog automation moved this from Untriaged to Done Aug 6, 2021
@msftbot msftbot bot locked as resolved and limited conversation to collaborators Sep 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

5 participants