Skip to content

Display specific error type during conventional commit validation mismatched #12

@aj3sh

Description

@aj3sh

The current validation only displays the error message: "Commit message does not follow conventional commits format." This message is challenging to understand as it does not pinpoint the exact error.

A more effective validation error could be provided, including specific details such as:

  • Type is missing
  • Scope cannot be empty
  • Header must not contain line breaks
  • etc.

These errors will assist in identifying the specific issue during the validation process.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions