@@ -24,7 +24,7 @@ source and target branches, and shows the information right on the merge request
Denied licenses will be clearly visible with an `x` red icon next to them
as well as new licenses which need a decision from you. In addition, you can
[manually allow or deny](#policies)
licenses in your project's license compliance policy section.
licenses in your project's license compliance policy section. If a `denied` license is newly committed it will disallow a merge request and instruct the developer to remove it.
NOTE: **Note:**
If the license compliance report doesn't have anything to compare to, no information
...
...
@@ -675,10 +675,9 @@ in your project's sidebar, and you'll see the licenses displayed, where:
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/22465) in [GitLab Ultimate](https://about.gitlab.com/pricing/) 12.9.
The **Policies** tab allows you to see your project's software license policies
and the associated classifications for each.
Policies allow you to specify licenses that are `allowed` or `denied` in a project. If a `denied` license is newly committed it will disallow a merge request and instruct the developer to remove it. Note, the merge request will not be able to be merged until the `denied` license is removed. You may add a [`License-Check` approval rule](#enabling-license-approvals-within-a-project), which enables a designated approver that can approve a merge request with `denied` license.
Policies can be configured by maintainers of the project.
The **Policies** tab in the projects license compliance section displays your project's license policies. Policies can be specified in this section by maintainers of the project.
