conventional-changelog / conventional-changelog/commitlint

feat: parsable output format

Open
#4,457 3 comments 0 reactions 0 assignees View on GitHub
feature help wanted
Dominant language
TypeScript
Stars
18.7k
Forks
970
Avg merge
7h 33m
Merged PRs (30d)
49

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

- [x] 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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.