conventional-changelog/commitlint

feat: parsable output format

Open

#4457 opened on Jun 15, 2025

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

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

Tech stack
typescriptnodejs
Domain
clideveloper 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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScript basicscommitlint formatter APINode.js CLI tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Start by examining the formatter API in packages/format. Look at how messages are currently structured and where line/column information could be added. The issue suggests adding line and column fields to the formatter output. Check existing formatter implementations to see how they could be extended. Then propose a change to include line and column numbers in the output.