GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Compatibility · Issue #16 · conventionalcommit/commitlint

Compatibility #16

New issue
Copy link
New issue
Copy link
Open
Open
Compatibility#16
Copy link

Description

@rubensa
rubensa
opened on Nov 24, 2023
Issue body actions

Node commitlint version seems to be the "de facto" standard Conventional Commits linter (but it forces you to have node installed).

Are there any plans to make this project compatible with it?

I mean at:

  • feature level
  • command parameter level
  • config file level

So it is easy to transition from the Node version to this Go version.

Reacted by Mateusz Łoskot
Reacted by Mateusz Łoskot

Activity

  1. muthukrishnan24 commented on Feb 21, 2026

    @muthukrishnan24
    muthukrishnan24
    on Feb 21, 2026
    Contributor
    More actions

    Hi
    yes, there was plan to match them but due to time constraint i couldn't.
    List top features you are missing in our commitlint?
    we will support them one by one.

  2. rubensa commented on Feb 23, 2026

    @rubensa
    rubensa
    on Feb 23, 2026
    Author
    More actions

    My main concern is not much about missing features but command line parameter and configuration compatibility.

    For example, for default rules I need:

    commitlint.config.js
    module.exports = { extends: ['@commitlint/config-conventional'] }

    for Node commitlint.

    But:

    commitlint.config.yaml
    # https://github.com/conventionalcommit/commitlint?tab=readme-ov-file#default-config
    version: v0.9.0
    formatter: default
    rules:
      - header-min-length
      - header-max-length
      - body-max-line-length
      - footer-max-line-length
      - type-enum
    severity:
      default: error
    settings:
      body-max-line-length:
        argument: 72
      footer-max-line-length:
        argument: 72
      header-min-length:
        argument: 10
      header-max-length:
        argument: 50
      type-enum:
        argument:
          - feat
          - fix
          - docs
          - style
          - refactor
          - perf
          - test
          - build
          - ci
          - chore
          - revert

    for Go commitlint.

    And I need to issue a commit-msg git hook like:

    commitlint --config commitlint.config.js --edit .git/COMMIT_EDITMSG

    for Node commitlint.

    But:

    commitlint lint --config commitlint.config.yaml < .git/COMMIT_EDITMSG

    for Go commitlint.

    Reacted by Mateusz Łoskot
  3. muthukrishnan24 commented on Feb 28, 2026

    @muthukrishnan24
    muthukrishnan24
    on Feb 28, 2026
    Contributor
    More actions

    you want go commitlint to be a dropin replacement for node commitlint? same cli flags, commands?

    you use --msg flag (--message or -m) flag instead of <

    commitlint lint --config commitlint.config.yaml --msg .git/COMMIT_EDITMSG
    

    i dont think js config support works for go commitlint,
    and simpler config, like extending defaults as requested in #12 in under development

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.