You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using @commitlint/config-lerna-scopes for helping commitlint to find the scope of Lerna to create conventional commits. Today, I noticed that after I changed the workspace configuration from packages/* to packages/** to support nested packages inside the packages folder, the package gathers all packages dependencies like typescript.
Expected Behavior
It should gives me only my packages inside my monorepo while using a nested packages folder approach like packages/**
The output of the scopes should be like this:
Hi there,
I am using
@commitlint/config-lerna-scopes
for helping commitlint to find the scope of Lerna to create conventional commits. Today, I noticed that after I changed theworkspace
configuration frompackages/*
topackages/**
to support nested packages inside thepackages
folder, the package gathers all packages dependencies liketypescript
.Expected Behavior
It should gives me only my packages inside my monorepo while using a nested packages folder approach like
packages/**
The output of the scopes should be like this:
✅ Prettied console output for expected scopes
Current Behavior
It gives me all packages even the dependencies of my subfolder packages.
Output is like that:
🚨 Prettied console output for current situation for scope names
Possible Solution
Steps to Reproduce (for bugs)
workspaces: ['packages/*']
toworkspaces: ['packages/**']
🗂️ commitlint.config.js
Context
Your Environment
commitlint --version
git --version
node --version
The text was updated successfully, but these errors were encountered: