Giter Site home page Giter Site logo

Comments (5)

vivaxy avatar vivaxy commented on June 15, 2024
  1. Please make sure you have installed @commitlint/config-conventional.
  2. Please make sure your commitlint config is valid. See Commitlint Website.

from vscode-conventional-commits.

Starraider avatar Starraider commented on June 15, 2024

I don't understand. Where do I have to install @commitlint/config-conventional?
I'm using Visual Studio Code with your vscode-conventional-commits extension, but I want to change the type-enum.
I don't have a Node project.

So where or how do I have to install @commitlint/config-conventional?

You write in your README: "Respect commitlint configs." So you don't read the commitlint.config.js?

from vscode-conventional-commits.

vivaxy avatar vivaxy commented on June 15, 2024

You have to install @commitlint/config-conventional in your project or in global.
And your commitlint.config.js is not valid. Please correct it according to Commitlint docs.

By design, vscode-conventional-commits extension does not install commitlint configs. Because there are lots of configs and lots of versions. If you'd like to use commitlint, please at least follow the commitlint config specification.

Here's some details about logic. The @commitlint/config-conventional preset represents some commitlint rules. The vscode-conventional-commits extension reads the config file, and finds out the preset rule name as @commitlint/config-conventional. But the extension does not know what exact the rules are, until it finds out the detailed @commitlint/config-conventional config files. You can install @commitlint/config-conventional in your project, which is recommended. Or you can copy the @commitlint/config-conventional rules to your commitlint.config.js.

Thank you for your question, looking forward to your response.

from vscode-conventional-commits.

Starraider avatar Starraider commented on June 15, 2024

Ok, thanks for you explanation.
I installed @commitlint/config-conventiona and fixed my commitlint.config.js and and it works.

Unfortunately after every "type" you put a colon ":", which is against the commit rules for TYPO3 projects. Is it possible to get rid of the colon?

from vscode-conventional-commits.

vivaxy avatar vivaxy commented on June 15, 2024

vscode-conventional-commits follows Conventional Commits which is not compatible with Commit Message rules for TYPO3 CMS. Maybe you can try to find or build another extension. 😃

from vscode-conventional-commits.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.