vivaxy/vscode-conventional-commits

💬Conventional Commits for VSCode.

VSCode Conventional Commits

Conventional Commits for VSCode.

Features

This extension helps you to fill in commit message according to Conventional Commits.

• Support commitlint configs. See Supported Commitlint Rules for details.
• Support auto commit and push after typing messages. See Commit Workflow for details.
• Support project level scope management.
• Support gitmojis.
• Support VSCode workspaces.

Usage

You can access VSCode Conventional Commits in two ways:

1. Command + Shift + P or Ctrl + Shift + P, enter Conventional Commits, and press Enter.
2. Click the icon on the Source Control menu. See the image below.

Extension Configuration

name	description	default
conventionalCommits.autoCommit	Control whether the extension should commit files after: forming the message or closing the editor tab. When #git.enableSmartCommit# enabled and #git.smartCommitChanges# was set to all, It allows to commit all changes when there are no staged changes. And set #git.postCommitCommand# to sync to run git.sync after commit.	true
conventionalCommits.emojiFormat	Specify which format will be shown in the gitmoji.	code
conventionalCommits.gitmoji	Control whether the extension should prompt for a gitmoji.	true
conventionalCommits.lineBreak	Specify which word will be treated as line breaks in the body. Blank means no line breaks.	""
conventionalCommits.promptBody	Control whether the extension should prompt for the body section.	true
conventionalCommits.promptFooter	Control whether the extension should prompt for the footer section.	true
conventionalCommits.promptCI	Control whether the extension should prompt for skipping CI run.	false
conventionalCommits.promptScopes	Control whether the extension should prompt for the scope section.	true
conventionalCommits.scopes	Specify available selections in the scope section.	[]
conventionalCommits.showEditor	Control whether the extension should show the commit message as a text document in a separate tab.	false
conventionalCommits.showNewVersionNotes	Control whether the extension should show the new version notes.	true
conventionalCommits.silentAutoCommit	Control that auto commit should be silent, without focusing source control panel.	false
conventionalCommits.editor.keepAfterSave	Control whether the extension should keep the editor tab open after saving the commit message.	false

Commit Workflow

The recommended workflow automatically add, commit and push files by default.

If you want the extension to only fill in the message, disable autoCommit configuration.

The Recommended Workflow

1. Active the extension.
2. Type messages.

The extension will automatically add the changed files, perform the commit and push the commit to remote.

How To Configure autoCommit

1. Enable Settings > conventionalCommits.autoCommit configuration of the extension. The extension enables Settings > conventionalCommits.autoCommit by default.
2. Enable Settings > git.enableSmartCommit and set Settings > git.smartCommitChanges to all to commit all changes when there are no staged changes.
3. Set Settings > git.postCommitCommand to sync to run git.sync after commit.

Supported Commitlint Rules

• body-full-stop
• body-leading-blank
• body-max-length
• body-max-line-length
• body-min-length
• footer-leading-blank
• footer-max-length
• footer-max-line-length
• footer-min-length
• header-case
• header-full-stop
• header-max-length
• header-min-length
• references-empty
• scope-enum
• scope-case
• scope-empty
• scope-max-length
• scope-min-length
• subject-case
• subject-empty
• subject-full-stop
• subject-max-length
• subject-min-length
• type-enum
• type-case
• type-empty
• type-max-length
• type-min-length
• signed-off-by

FAQ

Q: How do I add a line break in messages?

A: Set lineBreak configuration to \n. When you're typing, enter \n as a line break.

Or \\n in JSON format.

Q: How do I resolve repo not found error?

A: See issue discussion #15.

Q: How do I use commitlint in showEditor mode?

A: The extension - vscode-commitlint will helpful!

Troubleshooting

1. Switch to the VSCode OUTPUT tab, select Conventional Commits.
2. Copy all the output. Before sharing it, make sure you have removed all private information.

Contribution

1. The vscode task needs to install the extension - vscode-tsl-problem-matcher.
2. The effect of code changes needs to reactivate the extension. Just restart the task.

Team Members

• vivaxy
• yi_Xu

Financial Contributors

Become a financial contributor and help us sustain our community. [Contribute]

Individuals

Organizations

Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]

Related Projects

• gacp
• Commit Tagger
• vscode-commitizen
• Commit Message Editor
• commitji
• idea-conventional-commit
• Git-commit-plugin For Vscode

vscode-conventional-commits's Issues

[FEAT] "Confirm" GUI item for Description input

Is your feature request related to a problem? Please describe

Sometimes i want to simply select a preset for the commit message . If i do this using mouse, i still have to press Enter at the Description input .

Describe the solution you'd like

The easiest way could be the same type of list item that is used for option selection at other fields .

Additional context

Looking forward for: ability to set custom Types, from #93 .

[FEAT] Add conventionalCommits.types so its possible to change the default types.

Is your feature request related to a problem? Please describe.
Its not necessarily always a node project that uses conventional commits, meaning that its not always possible nor needed to install @commitlint/config-conventional and use commitlint.config.js.

Describe the solution you'd like
Just by adding the same pattern used for scopes would fix the issue, meaning that you could add to vscode settings:

conventionalCommits.types = [
    "chore",
    "docs"
]

Describe alternatives you've considered
Adding @commitlint/config-conventional as global using npm, and creating a "useless" commitlint.config.js file that is inside .gitignore.

[FEAT] About the icon

Is your feature request related to a problem? Please describe.
I'm really sorry on this personal preferences but the icon frustrate me lol.

Describe the solution you'd like
Maybe change the icon into the one that has the same design language as Microsoft's own codicon?

Describe alternatives you've considered
Or remove that red circle button on the "Source Control" toolbar?

Additional context

PS. I would love to do some PR on this. Thank You!

[FEAT] Default emoji for types

Is your feature request related to a problem? Please describe.
I wish to be able to add descriptions and default emoji for types.

Describe the solution you'd like
Using cz-emoji, you can set custom types in the .czrc file. For example:

{
  "path": "cz-emoji",
  "config": {
    "cz-emoji": {
      "conventional": true,
      "types": [
        {
          "emoji": "🚧",
          "code": ":construction:",
          "description": "Work in progress.",
          "name": "wip"
        },
        {
          "emoji": "🌟",
          "code": ":star2:",
          "description": "Adding features.",
          "name": "feature"
        },
        {
          "emoji": "🐛",
          "code": ":bug:",
          "description": "Fixing stuff.",
          "name": "fix"
        }
      ]
    }
  }
}

Describe alternatives you've considered
commitlint-config-gitmoji can add emoji in enum-types, but it isn't semantically valid and it wouldn't set the default icon for the types.

Additional context
Thank you for this great project. I would contribute with guidance.

Repo not found

Keep getting this error :
Conventional Commits: repo not found in path: /Users//Documents/projects

'Missing module' error notification

Hi,

Not sure if I am missing something but this is the error notification I see when attempting to do a commit via the extension.

[FEAT] add restricted configuration `conventionalCommits.promptDescription`

Is your feature request related to a problem? Please describe

Add restricted configuration conventionalCommits.promptDescription to disable the description section. But it will only work when the conventionalCommits.autoCommit setting to false or the conventionalCommits.showEditor setting to true. 😁

Describe the solution you'd like

I always edit the commit message as a text document in a separate tab. The large view is better than an input box. So I only need the choices of type, scope, and gitmoji, then I want to edit the main message rather than edit the description in the input box. 😊

Option to disable scope prompt

Is your feature request related to a problem? Please describe.
I do not use scopes in projects that are small.

Describe the solution you'd like
An option to disable scopes in the settings like for gitmoji by setting conventionalCommits.gitmoji : false would be greatly appreciated. Maybe conventionalCommits.promptScopes?

Describe alternatives you've considered
Pressing enter rapidly seems to be working for now.

[FEAT] improve modules that have dynamic `require` in webpack configuration

Here could add some reference links for solving this problem! 😀

sindresorhus/import-fresh#21

stackoverflow - add the magic comments to the import-fresh package

[FEAT] Add option to allow keeping edit status after saving the commit message

Is your feature request related to a problem? Please describe

When I use the conventionalCommits.showEditor option for making sure the commit message and I make a change, I always save it then check it again.
But the editor windows closed after I save the file. I think that checking again after saving the file is a common method to submit carefully to avoid possible errors again.

Describe the solution you'd like

Could we add an option to allow keep edit status until windows close?

Describe alternatives you've considered

If the option set to true and needs to auto-commit, The workflow will also be doing after the windows close.

Additional context

The option name could be conventionalCommits.editor.keepAfterSave, it can be true or false. default to false.

[BUG] generate failed when make a patch version update

The changelog-reader-action can not read the third level heading, in which case the workflows failed when make a patch version update.

[FEAT] use action to build vsix and release

Make package to release for offline usage.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): replace dependency standard-version with commit-and-tag-version ^9.5.0
• chore(deps): update mindsers/changelog-reader-action action to v2.2.3
• chore(deps): update actions/github-script action to v7
• chore(deps): update actions/upload-artifact action to v4
• chore(deps): update dependency @types/node to v20
• chore(deps): update dependency husky to v9
• chore(deps): update dependency lint-staged to v15
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/github-script action to v6.4.1
• chore(deps): update actions/upload-artifact action to v3.1.3
• chore(deps): update actions/checkout action to v3.6.0
• chore(deps): update actions/setup-node action to v3.8.2
• chore(deps): update dependency ovsx to ^0.9.0
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency webpack-cli to v5
• fix(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional, @commitlint/load, @commitlint/rules)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/build.yml

• actions/checkout v3.3.0
• actions/setup-node v3.6.0
• actions/github-script v6.4.0
• actions/upload-artifact v3.1.1
• actions/upload-artifact v3.1.1

.github/workflows/post-build.yml

• actions/github-script v6.4.0
• actions/github-script v6.4.0
• actions/github-script v6.4.0
• actions/github-script v6.4.0

.github/workflows/prepare-release.yml

• actions/github-script v6.4.0
• actions/checkout v3.3.0
• actions/setup-node v3.6.0
• actions/github-script v6.4.0
• mindsers/changelog-reader-action v2.2.2
• actions/github-script v6.4.0

.github/workflows/release.yml

• actions/checkout v3.3.0
• actions/setup-node v3.6.0
• actions/github-script v6.4.0
• mindsers/changelog-reader-action v2.2.2
• actions/create-release v1.1.4
• actions/upload-release-asset v1.0.2

npm

package.json

• @commitlint/cli ^13.0.0
• @commitlint/config-conventional ^13.0.0
• @commitlint/load ^13.0.0
• @commitlint/rules ^13.0.0
• @yi-xu-0100/conventional-commit-types-i18n 1.6.0
• @types/node ^16.0.0
• @types/vscode ^1.44.0
• @vscode/vsce ^2.16.0
• clean-webpack-plugin ^4.0.0
• husky 8
• lint-staged ^13.0.0
• ovsx ^0.5.0
• pinst ^3.0.0
• prettier ^2.0.2
• standard-version ^9.0.0
• string-replace-loader ^3.0.1
• ts-loader ^9.0.0
• typescript ^5.0.0
• warnings-to-errors-webpack-plugin ^2.0.1
• webpack ^5.76.0
• webpack-cli ^4.5.0
• vscode ^1.44.0

---

• Check this box to trigger a request for Renovate to run again on this repository

[FEAT] Make it compatible with python's commitizen configuration

Is your feature request related to a problem? Please describe

I prefer python's implementation of commitizen, as it seems easier to understand and less language-specific.

It allows to be configured easily, without using a node-specific file such as package.json: https://commitizen-tools.github.io/commitizen/config/

Describe the solution you'd like

It would be nice if this extension understood those configurations, so I'd get the same experience from the extensions and from CLI.

Describe alternatives you've considered

Configuring twice (what else could I do? 🤷🏼‍♂️)

Persist the prompts

Hi, loving your extension!

Although, there is a little UX issue that is important to fix IMO. When I'm doing steps, especially writing the commit message, I usually need to check the issue/task number, files, etc. Any click outside the prompt closes it and I have to start everything over 🙁

support no emoji

[BUG] Missing icon after VSCode update 1.56

Describe the bug

After last VSCode update which changes icons, Conventional Commits plugin icon is also not rendering correctly. There is only a few pixels in heigh where you can click on it.

To reproduce

Steps to reproduce the behavior:

1. Update VSCode to 1.56.
2. Install Conventional Commits plugin.
3. Go to Source Control tab.
4. See missing icon (only little lighter small dot instead icon).

Expected behavior

Default Conventional Commits plugin icon should be rendered.

Screenshots

Application logs

[info] Extension Activated
[info] vscode.env.language: en
[info] last used version: 1.21.0
[info] Conventional commits started.
[info] VSCode version: 1.56.0
[info] Git version: 1.0.0
[info] VSCode Conventional Commits version: 1.21.0
[info] conventionalCommits.autoCommit: true
[info] conventionalCommits.emojiFormat: code
[info] conventionalCommits.gitmoji: true
[info] conventionalCommits.lineBreak: 
[info] conventionalCommits.promptBody: true
[info] conventionalCommits.promptFooter: true
[info] conventionalCommits.promptScopes: true
[info] conventionalCommits.showEditor: false
[info] conventionalCommits.showNewVersionNotes: true
[info] conventionalCommits.editor.keepAfterSave: false
[info] git.enableSmartCommit: false
[info] git.smartCommitChanges: all
[info] git.postCommitCommand: none

[BUG] '\n' not work for line break

Describe the bug

When I set the conventionalCommits.lineBreak as '\n', it does not work for me.

To reproduce

1. win10 Professional 20H2
2. setting about conventionalCommits:

   "conventionalCommits.autoCommit": false,
   "conventionalCommits.emojiFormat": "emoji",
   "conventionalCommits.lineBreak": "\n",

Expected behavior

Just like the readme says: Set lineBreak configuration to \n. When you're typing, enter \n as a line break.

Screenshots

Application logs

Started
VSCode version: 1.53.2
VSCode Conventional Commits version: 1.13.0
Git version: 1.0.0
autoCommit: false
gitmoji: true
emojiFormat: emoji
scopes: 
lineBreak: 

git.enableSmartCommit: true
git.smartCommitChanges: all
git.postCommitCommand: none
arg: d:\4 Creation\github\repo-list-generator
git.repositories: d:\4 Creation\github\repo-list-generator
workspacceFolders: d:\4 Creation\github\repo-list-generator
commitlintRuleConfigs: {}
commitMessage: {
  "_type": "fix",
  "_scope": "",
  "_gitmoji": "🐛",
  "_subject": "test line break",
  "_body": "test\\ntest\\n",
  "_footer": "test\\ntest\\n"
}
message: fix: 🐛 test line break

test\ntest\n

test\ntest\n
inputBox.value: fix: 🐛 test line break

test\ntest\n

test\ntest\n
Finished successfully.

Line break

I have picked \n for line break . It does work but how to remove the empty space after the new line .
with this line 1 \n line 2
I get

[FEAT] Optional autoinsert of jira issue derived from branchname

Is your feature request related to a problem? Please describe

I always reference the jira issue like ABC-123 manually.

Describe the solution you'd like

It would be nice to have an option that would get the jira issue from the branchname that looks mostly like feature/ABC-123-long-description-of-issue

Describe alternatives you've considered

Maybe some kind of footer list like the scope list would work also so you can save a footer and insert it on every commit again.

[FEAT] Settings to remove unused options

Is your feature request related to a problem? Please describe.
Hi, Thank you for creating this awesome extension. I've been using it for quite some time and one thing that bothers me is spamming through "enter" on sections that I never complete.

For example:

• Type of change: chore
• Scope: (issue number)
• Emoji: 📝
• short description: Update documentation
• longer description:
• breaking changes:

Describe the solution you'd like
It would be nice if we could have all 6 options as a setting checkbox to define if it will appear in the 1/6 commit options with each option default set to true or checked.

it looks like we have some of the options already done (Emoji and Scopes) but it would be nice for all options.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Extension icon is invisible after VSCode update v1.40

Describe the bug
Extension icon (pink circle) is not visible in latest VSCode, clicking on the icon space works fine though.

To reproduce

1. Install latest VSCode
2. Install latest VSCode Conventional Commits extension
3. Open Source Control view
4. No icon is visible on the pane header

Expected behavior
Icon should be visible - right?

Screenshots
If applicable, add screenshots to help explain your problem.

[FEAT] Retry last commit

Is your feature request related to a problem? Please describe

Occasionally, a commit may fail for whatever reason (hook failure, GPG signing error etc)

Describe the solution you'd like

It would be nice to be able to retry the previous failed commit (like commitizen has cz --retry) instead of having to fill out the entire commit again.

[QUESTION] Commitlint scope-enum

Hi vscode-conventional-commits contributors, I am a maintainer over at commitlint. We have been putting together a PR to introduce regexs in to the scope-enum rule. I thought I would dorp you a message to see if you had any comments on the PR, and anything we can do to make our tool integrate better with yours.

conventional-changelog/commitlint#1257

support auto add, commit or sync

[BUG] missing fallback translation when no locale available

As the description in here. I find that it may throw an Error when using @yi-xu-0100/[email protected].

So I think that it should be hot fixed in a new version.

[BUG] publish action failed

See https://github.com/vivaxy/vscode-conventional-commits/runs/2082721472.

Maybe I need to move the step of push commit to the publishing. 😅

Could you test this step locally for setting the env?

The good news is the v1.16.1 will not appear in release. 😀

Add setting option to change case of first word in commit

Also chenge first latter manualy

[BUG] Emoji codes don't work with anything besides GitHub

The extension supports git emojis but adds them as emoji codes, not as Unicode characters. This only works in GitHub and GitLab, other Git providers like Azure DevOps does not support them.

Also, even the most basic usage of commit descriptions (git log in terminal) does not support emoji codes:

The only workaround for it is to mannualy edit the commit message and replace it by corresponding emoji as Unicode.

Highlights:

• gitmoji-cli supports configuration to choose from emojicodes or Unicode
• rumoji encodes/decodes emoji codes and could be useful to fix this problem

The only advanced workaround I think for it is to create a commit-msg hook and convert the codes to characters using rumoji.

Support commitlint

[FEAT] use manually scope for commit

Is your feature request related to a problem? Please describe.

When I make commit to another open-source project, I may use the scope but do not want to create a setting for workspace.

Describe the solution you'd like

The scope typed here can be used for the current commit.

Fillout scopes from commitlint.config.js

Thank you for a nice extension! Probably the most needed thing there is to be able to select one of the predefined scopes from commitlint config file. As I see it could be easily done with filling items in prompt function from commitlint.getRule('scope-enum'). I could add a PR a bit later, never tried to debug a VSCode extension so it could take some time :) But if you will be able to add it earlier - many thanks from me and my team!

[FEAT] short description input should limit the max length according to the setting "header-max-length"

short description input should limit the max length according to the setting "header-max-length"

Describe the solution you'd like
Add a max length limit to the input element or as least give users some prompt information.

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)

[FEAT] use conventional-commit-types-i18n to localize the types

Is your feature request related to a problem? Please describe.

I found the conventional-commit-types description still not localized.

Describe the solution you'd like

I create a package @yi-xu-0100/conventional-commit-types-i18n and may give you a favor.

Describe alternatives you've considered

I only creat the zh-cn and the en for the first publish, any dialogue about it can give here.

Additional context

This is my first npm package, and I try to make it useful. 😀

[BUG] If the `promptScopes` changed, the context of `scope` will be retained

Describe the bug
If the promptScopes changed, the context of scope will be retained.

To reproduce
Steps to reproduce the behavior:

1. Set promptScopes as true.
2. make a commit with scope.
3. Set promptScopes as false.
4. make a commit and there will have the scope last used in the message.

Expected behavior

The scope should empty when the promptScopes as false.

[FEAT] automatically prepend `BREAKING CHANGE: `

Is your feature request related to a problem? Please describe.
While the extension explicitly prompts the user to enter any breaking changes, it expects you to prepend BREAKING CHANGE: manually. In my opinion this is a cumbersome task that should be automated.

Describe the solution you'd like
A possible solution would be to simply prepend BREAKING CHANGE: automatically, if the user writes something when prompted for breaking changes.

Describe alternatives you've considered
A simpler, but in my opinion inferior, solution would be to no longer ask for a text value for breaking changes. This could be replaced by asking whether or not there were breaking changes and then adding an exclamation mark to the description when there are.

Nothing happens :-(

Hi! I'm trying to commit using this package but nothing happens after I input all the info. Here's a gif:

Everything is up-to-date.

Thanks in advance and congratulations!

[FEAT]An option to set the gitmoji position

Is your feature request related to a problem? Please describe

Ya, I think it's a problem for me and my team.

Describe the solution you'd like

Put emoji at the beginning of the commit message.

Describe alternatives you've considered

An option to set the gitmoji position

Additional context

Thanks very much!

[BUG] validation for subject-max-length is not calculated the same as commitlint

Describe the bug

It seems like commitlint calculates the subject-max-length flag by adding all the characters of the first line, including the type, scope and gitmoji characters. When entering a subject, the character count for a custom subject-max-length is only validated against the subject text.

To reproduce

Steps to reproduce the behavior:

1. Add the following rule to the .commitlintrc.js config file:

'subject-max-length': [2, 'always', 50]

2. Start a commit.
3. Select build
4. Select None
5. Select 🚨:rotating_light:
6. Enter: this subject is less than 50 characters - with error
7. Remove - with error from the text box to put the subject character count under 50 to proceed
8. Proceed with the commit with blank entries for the other fields

Result

commitlint errors out with the following:

Current branch is "develop".
⧗   input: build: :rotating_light: this subject is less than 50 characters
✖   subject must not be longer than 50 characters [subject-max-length]

Expected behavior

Length validation on the subject input field should take into account: build: :rotating_light: and not allow the user to proceed.

Package Info

"@commitlint/cli": "9.1.2",
"@commitlint/config-conventional": "9.1.2",

[FEAT] Configure subject length

Is your feature request related to a problem? Please describe.
Typed a description that was too long and GitHub split it into 2 lines with (...) on 2nd line

Describe the solution you'd like
Would be nice to have a config with max

Describe alternatives you've considered
I don't know of any alternatives

Additional context
VSCode already has this setting Git: Input Validation Subject Length that we can configure.

and the Commitizen VSCode plugin also have a similar setting

So it would be really nice if this great plugin also include such setting or use the default VSCode setting.
It would be helpful to know when we reach the length limit so that we don't end up having it split

Thank you for the great plugin, work as expected, this would just make it more awesome 😄

Extension causes high cpu load

[vivaxy.vscode-conventional-commits-unresponsive.cpuprofile.txt]
(https://github.com/vivaxy/vscode-conventional-commits/files/5897322/vivaxy.vscode-conventional-commits-unresponsive.cpuprofile.txt)

• Issue Type: Performance
• Extension Name: vscode-conventional-commits
• Extension Version: 1.13.0
• OS Version: Windows_NT x64 6.1.7601
• VSCode version: 1.52.1

⚠️ Make sure to attach this file from your home-directory:
⚠️e:\Users\Clixer\AppData\Local\Temp\vivaxy.vscode-conventional-commits-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

[BUG] emojiFormat prefer code mode should set in the workspace

I find that the emojiFormat prefers code mode before, and it can be set into the workspace for the later pull request.

Support remember previous scopes

Support manage scopes settings.
Support scopes shared from vscode configurations.

[BUG] Extenstion stopped recognizing commitlint rules

Describe the bug
Since yesterday the extension stopped recognizing configured scopes and other settings for me and my colleagues. Unfortunately I have no idea why, nothing has changed about the setup of the repository or the configurations themselves. Have there been any recent changes to the extensions which may have caused it? The last working version for us seems to be 1.16.1.

Application logs

Activated
vscode.env.language: en
[warning] getNLS: Missing translation for en
Started
VSCode version: 1.54.3
VSCode Conventional Commits version: 1.18.0
Git version: 1.0.0
autoCommit: true
gitmoji: false
emojiFormat: code
scopes: 
lineBreak: 
promptScopes: true
git.enableSmartCommit: true
git.smartCommitChanges: all
git.postCommitCommand: none
arg: undefined
git.repositories: /home/redacted
workspaceFolders: /home/redacted
commitlintRuleConfigs: {}

[FEAT] Being able to configure gitmoji

Is your feature request related to a problem? Please describe.
The amount of Gitmoji is simply staggering. It makes it harder to find what you're looking for.

Some options are too precise, for example I want just one entry for dependencies instead of 5 (add, remove, upgrade, downgrade, fix version). The short description is perfectly fine to explain what was done with the dependency.

There are plenty of useless gitmojis (drunken code, write bad code, etc.) It's just adding to the noise and making it harder to sort through the 5 to 15 gitmojis I really use.

Describe the solution you'd like
I would like to be able to add and remove gitmojis from the list. The configuration should be available through the VSCode settings.json file.

Describe alternatives you've considered
I've tried all the other VSCode extensions, they're simply not complete and are missing stuff.

Ironically, this extension is too complete ;)

Additional context
Your extension is awesome already, it's really the easiest to use when it come to UX.

[FEAT]Can support custom type of committing change?

Describe the solution you'd like
Now I can only choose type one of feat,fix,docs... Can support custom type?

[FEAT] : Publish the extension to the Open VSX Registry

Hello,

I think it would be interesting to publish your wonderful extension in the VSX Registry. This will allow people using GitPod, or Code-Serve, to use your extension in their browser... What do you think about it ?

[BUG] commitlint.config.js gets ignored

Describe the bug

My commitlint.config.js gets ignored.

Maybe you can provide a sample file how the commitlint.config.js has to look like to make it work?

To reproduce

Steps to reproduce the behavior:

1. Install extension
2. Restart VS Code
3. Make new commitlint.config.js
4. Add some rules
5. Test commit

Here you can find my commitlint.config.js

Expected behavior

My type-enums should be displayed, but they are not.

Application logs

Started
VSCode version: 1.49.0-insider
VSCode Conventional Commits version: 1.11.0
Git version: 1.0.0
autoCommit: true
gitmoji: false
emojiFormat: code
scopes: deployer
lineBreak: 
git.enableSmartCommit: true
git.smartCommitChanges: all
git.postCommitCommand: sync
arg: /Users/sven/Documents/Projekte/devTypo3ddev
git.repositories: /Users/sven/Documents/Projekte/devTypo3ddev
workspacceFolders: /Users/sven/Documents/Projekte/devTypo3ddev
commitlintRuleConfigs: {}
commitMessage: {
  "type": "test",
  "scope": "",
  "gitmoji": "",
  "subject": "Fix commitlint.config.js",
  "body": "",
  "footer": ""
}
message: test: Fix commitlint.config.js
inputBox.value: test: Fix commitlint.config.js
Finished successfully.

Possible to add new lines in detailed description?

First of all, thanks for creating this extension, it adds a lot of value to my workflow! 🎉 🙏

I wanted to ask whether it is possible to add new lines in the detailed description prompt, since I currently always have to git commit --amend afterwards to format it correctly in case I want to have new lines in between some parts.

I understand that Visual Studio Code might not allow for a multi-line prompt (I didn't check), but how about adding an identifier which translates into a new line in the commit message, e.g. \n?