conventional-changelog/commitlint

feat: parsable output format

Open

#4,457 opened on Jun 15, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (896 forks)batch import
featurehelp wanted

Repository metrics

Stars
 (15,497 stars)
PR merge metrics
 (Avg merge 12h 56m) (52 merged PRs in 30d)

Description

Expected Behavior

Commitlint prints line and column numbers where the issue was found, to allow parsing the output for IDE integration (for example vim with neomake), like all major linters do. This should be the default behaviour TBH.

Current Behavior

Commitlint cat-s the message and writes issues found without any context. Formatter doesn't support line and column fields.

Affected packages

  • cli
  • core
  • prompt
  • config-angular

Possible Solution

At least line and column fields should be available in the formatter API.

Context

No response

Contributor guide

Research direction
Explore the existing formatter API in commitlint to add line and column fields, then update output formatters to include these fields.
Tech stack
typescriptnodejs
Domain
cli
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60