Skip to content

OSADL project-license check improvements#11996

Open
sschuberth wants to merge 3 commits into
mainfrom
osadl-project-license-check-imps
Open

OSADL project-license check improvements#11996
sschuberth wants to merge 3 commits into
mainfrom
osadl-project-license-check-imps

Conversation

@sschuberth

Copy link
Copy Markdown
Member

Please have a look at the individual commit messages for the details.

Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.io>
This is a preparation for adding the "second form" of OSADL check [1].

[1]: #5987 (comment)

Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.io>
Add a simple diagram to highlight how the current check with the OSADL
matrix is implemented.

Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.io>
@sschuberth sschuberth requested a review from a team as a code owner June 12, 2026 09:36
@sschuberth sschuberth enabled auto-merge (rebase) June 12, 2026 09:36
@codecov

codecov Bot commented Jun 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.53%. Comparing base (4c2b946) to head (2f04914).
⚠️ Report is 227 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main   #11996   +/-   ##
=========================================
  Coverage     58.53%   58.53%           
+ Complexity     1822     1820    -2     
=========================================
  Files           361      361           
  Lines         13540    13540           
  Branches       1396     1396           
=========================================
  Hits           7925     7925           
  Misses         5115     5115           
  Partials        500      500           
Flag Coverage Δ
funTest-no-external-tools 30.13% <ø> (-0.09%) ⬇️
test-ubuntu-24.04 42.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.


// Define a rule that is executed for each license of the dependency.
licenseRule("OSADL_PROJECT_LICENSE_COMPATIBILITY", licenseView) {
licenseRule("OSADL_PROJECT_LICENSE_RULE", licenseView) {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't get the idea why the new name is better.

The intention is to check if license in any dependency is compatible with the project license. So, the name before fit better?


// Define a rule that is executed for each dependency.
dependencyRule("OSADL_MATRIX_COMPATIBILITY") {
dependencyRule("OSADL_PROJECT_LICENSE_DEPENDENCY_RULE") {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In ort-config we always use the same name for the outer rule and the innder rule, and outer and inner always correspond to the "same" rule.

Should we follow this pattern here too?

Imho this is less misleading, as currently this is IIUC semantically just one rule, and no potentially flagged violation would ever use "OSADL_PROJECT_LICENSE_DEPENDENCY_RULE" as the source.

What do you think?

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.

2 participants