Skip to content

Conventional commits #104

Description

@lkstrp

Should we enforce conventional commits for every squashed PR's commit message? Commits on a branch which are going to be squashed can look like preferred. But on the master branch it keeps history consistent and lets us auto generate release notes much better. Strict semver versioning probably doesn't matter much for an app like this, but I think it's in general a good convention

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs discussionRequires discussion before further action

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions