We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using typescript config files with commitlint, the Conventional Commits extension does not load configuration.
Steps to reproduce the behavior:
const Configuration = { rules: { 'type-enum': [2, 'always', ['javascript', 'example']] } } module.exports = Configuration
import { UserConfig } from '@commitlint/types' const Configuration: UserConfig = { rules: { 'type-enum': [2, 'always', ['typescript', 'example']] } } export default Configuration
Config should be loaded from typescript config files as described in commitlint docs
[info] Extension Activated [info] vscode.env.language: en [info] last used version: 1.24.0 [info] Conventional commits started. [info] VSCode version: 1.66.2 [info] Git version: 1.0.0 [info] VSCode Conventional Commits version: 1.24.0 [info] conventionalCommits.autoCommit: true [info] conventionalCommits.silentAutoCommit: false [info] conventionalCommits.emojiFormat: code [info] conventionalCommits.gitmoji: true [info] conventionalCommits.lineBreak: [info] conventionalCommits.promptBody: true [info] conventionalCommits.promptCI: false [info] conventionalCommits.promptFooter: true [info] conventionalCommits.promptScopes: true [info] conventionalCommits.scopes: [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 [info] arg: undefined [info] git.repositories: /Users/jay/dev/demo_project [info] workspaceFolders: /Users/jay/dev/demo_project [info] Load commitlint configuration successfully. [info] commitlintRuleConfigs: {}
The text was updated successfully, but these errors were encountered:
@jaytavares Thanks for the notice.
@commitlint/load we depend on is v13.1.0, which does not support loading TypeScript config files. While @commitlint/[email protected] supports this. conventional-changelog/commitlint@b65aced
Sorry, something went wrong.
vivaxy
No branches or pull requests
Describe the bug
When using typescript config files with commitlint, the Conventional Commits extension does not load configuration.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Config should be loaded from typescript config files as described in commitlint docs
Application logs
[info] Extension Activated
[info] vscode.env.language: en
[info] last used version: 1.24.0
[info] Conventional commits started.
[info] VSCode version: 1.66.2
[info] Git version: 1.0.0
[info] VSCode Conventional Commits version: 1.24.0
[info] conventionalCommits.autoCommit: true
[info] conventionalCommits.silentAutoCommit: false
[info] conventionalCommits.emojiFormat: code
[info] conventionalCommits.gitmoji: true
[info] conventionalCommits.lineBreak:
[info] conventionalCommits.promptBody: true
[info] conventionalCommits.promptCI: false
[info] conventionalCommits.promptFooter: true
[info] conventionalCommits.promptScopes: true
[info] conventionalCommits.scopes:
[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
[info] arg: undefined
[info] git.repositories: /Users/jay/dev/demo_project
[info] workspaceFolders: /Users/jay/dev/demo_project
[info] Load commitlint configuration successfully.
[info] commitlintRuleConfigs:
{}
The text was updated successfully, but these errors were encountered: