Configure license approval rules with regex or wildcard pattern
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
Today it is required to define approved/denied licenses 1 by 1, which may require frequent updates to the policy.
Intended users
User experience goal
Proposal
Offer a way to configure rules with regex or a wildcard pattern so you can define a rule such as:
instead of saying AGPL-1.0, 1.1 etc. it would just be supporting AGPL* which would then block any version of AGPL (including future releases).
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.