summaryrefslogtreecommitdiff
path: root/doc/development/licensing.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-04-20 23:50:22 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-04-20 23:50:22 +0000
commit9dc93a4519d9d5d7be48ff274127136236a3adb3 (patch)
tree70467ae3692a0e35e5ea56bcb803eb512a10bedb /doc/development/licensing.md
parent4b0f34b6d759d6299322b3a54453e930c6121ff0 (diff)
downloadgitlab-ce-9dc93a4519d9d5d7be48ff274127136236a3adb3.tar.gz
Add latest changes from gitlab-org/gitlab@13-11-stable-eev13.11.0-rc43
Diffstat (limited to 'doc/development/licensing.md')
-rw-r--r--doc/development/licensing.md7
1 files changed, 2 insertions, 5 deletions
diff --git a/doc/development/licensing.md b/doc/development/licensing.md
index c467fe81755..1ab56e60a0b 100644
--- a/doc/development/licensing.md
+++ b/doc/development/licensing.md
@@ -18,9 +18,6 @@ Some gems may not include their license information in their `gemspec` file, and
### License Finder commands
-NOTE:
-License Finder currently uses GitLab misused terms of `whitelist` and `blacklist`. As a result, the commands below reference those terms. We've created an [issue on their project](https://github.com/pivotal/LicenseFinder/issues/745) to propose that they rename their commands.
-
There are a few basic commands License Finder provides that you need in order to manage license detection.
To verify that the checks are passing, and/or to see what dependencies are causing the checks to fail:
@@ -32,13 +29,13 @@ bundle exec license_finder
To allowlist a new license:
```shell
-license_finder whitelist add MIT
+license_finder permitted_licenses add MIT
```
To denylist a new license:
```shell
-license_finder blacklist add Unlicense
+license_finder restricted_licenses add Unlicense
```
To tell License Finder about a dependency's license if it isn't auto-detected: