GitHub puts enterprise license rules into merge checks
Enterprise Cloud repositories using Code Security can now apply GitHub’s generally available open-source license checks. Administrators can apply a shared license policy and require a check before merging dependency changes. Developers see noncompliant packages in pull requests, while policy managers handle review requests. New programmatic checks also let coding agents ask whether a package complies before incorporating it.
Artificial Intelligence··Evening
GitHub makes central license checks generally available
According to GitHub’s announcement, Enterprise Cloud customers using Code Security can now apply the generally available license-compliance feature from software-development platform GitHub. The feature extends dependency review into an enterprise-wide license policy, including environments that keep data in specified regions. Administrators can target repositories with a rule requiring license-compliance results before a change is merged.[1]
Pull requests flag dependencies outside the policy
When a pull request adds or modifies a dependency, the check compares the package with the central policy and annotates noncompliant packages. A developer can remove or replace the dependency, amend the policy or request a package exception. A designated license-manager role reviews closure requests, receives email notifications and handles pending cases in the enterprise console.[1]
Package queries let coding agents check rules in advance
Since the public preview in June, GitHub has added license data to dependency graphs and Software Bill of Materials exports for data-residency customers. Policy changes now emit audit-log events. New application programming interfaces download, update or replace a policy. A package-compliance query lets coding agents check acceptability before recommending or incorporating a dependency.[1]
