Skip to content

Conversation

@plorenz
Copy link
Member

@plorenz plorenz commented Jan 31, 2025

No description provided.

@plorenz plorenz requested a review from a team as a code owner January 31, 2025 15:48
@plorenz plorenz force-pushed the license-check branch 2 times, most recently from 4358dda to 2247011 Compare January 31, 2025 15:55
Copy link
Member

@andrewpmartinez andrewpmartinez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is ...fine. Ideally, it would have been nice to have a whitelist/blacklist. But that might be hard to maintain.

I assume the idea here is that if the licenses change in any way, someone has to go and add their licenses to the expected list, which hopefully get flagged in a PR.

@plorenz
Copy link
Member Author

plorenz commented Jan 31, 2025

This is ...fine. Ideally, it would have been nice to have a whitelist/blacklist. But that might be hard to maintain.

I assume the idea here is that if the licenses change in any way, someone has to go and add their licenses to the expected list, which hopefully get flagged in a PR.

Yes, exactly. I wouldn't expect that to happen often, since most projects should fall under the set already tracked.

@plorenz plorenz merged commit 1b51fda into main Jan 31, 2025
6 checks passed
@plorenz plorenz deleted the license-check branch January 31, 2025 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants