From de2d154265ae32d4feebfd74b6e448fec620d1b9 Mon Sep 17 00:00:00 2001 From: vivaxy Date: Fri, 10 Apr 2020 09:11:48 +0800 Subject: [PATCH] docs: add VSCode Conventional Commits --- content/v1.0.0/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/v1.0.0/index.md b/content/v1.0.0/index.md index 698bfab..8b83573 100644 --- a/content/v1.0.0/index.md +++ b/content/v1.0.0/index.md @@ -210,6 +210,7 @@ Configurable and usable for PHP projects as a composer dependency or usable glob * [Git Commit Template](https://plugins.jetbrains.com/plugin/9861-git-commit-template): Add Conventional Commits support to [JetBrains Editors](https://www.jetbrains.com/) (IntelliJ IDEA, PyCharm, PhpStorm...). * [commitsar](https://github.com/commitsar-app/commitsar): Go tool for checking if commits on branch are Conventional Commits compliant. Comes with Docker image for CI uses. * [semantic-release](https://github.com/semantic-release/semantic-release): A tool that automates the whole package release workflow including: determining the next version number, generating the release notes and publishing the package. +* [VSCode Conventional Commits](https://marketplace.visualstudio.com/items?itemName=vivaxy.vscode-conventional-commits): Add Conventional Commits supports for VSCode. ## Projects Using Conventional Commits