-
It seems to me that since the spec lives here, so should the parser. Thoughts?
Having separate issues and history from the monorepo where it lives today would be helpful for me, as I have been str…
-
Hi,
I was trying out this action on [this workflow](https://github.com/victor-rds/KeeTrayTOTP/runs/560065082) and got an error during the generation of the changelog. This was the first time runnin…
-
https://github.com/conventional-changelog/conventional-changelog/pull/599
Now getting the following in CI `error conventional-recommended-bump@6.0.9: The engine "node" is incompatible with this mod…
-
Hi,
I just took a quick look at the type definition for `Commit` used in `@commitlint/parse`, I don't see information related to breaking changes present. Could we support this?
I think either b…
akphi updated
3 years ago
-
To provide actionable debug information and errors, we should implement Position tracking, as defined in [uninst](https://github.com/syntax-tree/unist#position).
Refs: https://github.com/convention…
-
## CVE-2020-8116 - High Severity Vulnerability
Vulnerable Libraries - dot-prop-4.2.0.tgz, dot-prop-3.0.0.tgz
dot-prop-4.2.0.tgz
Get, set, or delete a property from a nested object using a dot path…
-
It would make it much easier for upstream tooling to use this parser, if we provide a helper that converted the tree into [conventional-changelog-parser](https://www.npmjs.com/package/conventional-com…
-
Right now it doesn't compile due to some issues with `toascii(wxString[n])`, but this shouldn't be difficult to fix. This will almost certainly not be the last problem, however.
-
## Expected Behavior
Currently when we have a Git hook (sh script) with only `commitlint` as command, it fails to fall back to `COMMIT_EDITMSG`.
## Current Behavior
It fails with `[in…
-
**Context**
GitHub [finally fixed](https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/#improvements-for-public-repository-forks) the [issue](https://dev.to…