Initialize a project with conventional commits, commitizen, and commit linting
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
packages
.editorconfig
.eslintignore
.eslintrc.js
.gitattributes
.gitignore
.travis.yml
.yo-rc.json
CHANGELOG.md
LICENSE
README.md
commitizen.config.js
commitlint.config.js
lerna.json
package.json
yarn.lock

README.md

Create Semantic Module

Build Status Coverage percentage

create-semantic-module makes it easy to start using conventional commits in new or existing projects.

Adding conventional commits to your development workflow can be a big change when you work on a project with multiple contributors.

Tools like commitizen and commitlint do a great job of easing this transition, but configuring them to work together requires some boilerplate. That's where create-semantic-module comes in!

Usage

Generate a new project:

yarn create semantic-module my-module-name

Or run from within an existing project:

cd ./my-module-name
yarn create semantic-module

If using npm 5.2.0 or later, you can also use npx:

npx create-semantic-module my-module-name

License

MIT © Jacob LeGrone