conventional-changelog/commitlint

When use @commitlint/config-pnpm-scopes how to add extra valid scopes that not are a workspace name?

Open

#3658 opened on Aug 25, 2023

View on GitHub
 (1 comment) (3 reactions) (0 assignees)TypeScript (15,497 stars) (896 forks)batch import
communityhelp wantedquestion

Description

This issue does not include a description.

Contributor guide

Tech stack
typescriptnodejs
Domain
toolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of commitlintUnderstanding of pnpm workspaces
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Look into the @commitlint/config pnpm scopes documentation and the commitlint configuration options for custom scopes. Check the existing comment on the issue for any hints. Examine the default configuration file and how scopes are validated.