Skip to content

Considering enforcing conventional commit specification #4891

@Fdawgs

Description

@Fdawgs

Prerequisites

  • I have written a descriptive issue title
  • I have searched existing issues to ensure the issue has not already been raised

Issue

Whilst the release notes are great at showing what changed and who committed what, the individual items are a mixed bag, and make it difficult to skim read.

As an example from v4.19.0:
image

From a glance, I can't tell what that pluginName will be exposed in FastifyInstance change is. Is it a bugfix? Is it a new feature? Was it just the documentation that was updated? The other two items in the list I can clearly see what type of change they were.

I think this could be remedied by enforcing the use of the conventional commit specification using the Angular convention with commitlint in a husky hook and/or the commitlint GH Action.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions