-
- [x] PRs create a preview with data from `staging`
- [x] Commits to `master` deploy to production
- [ ] Unit tests & API tests run on every PR
- [ ] e2e tests run pre-deploy on commit to `master`…
-
-
```
import { bootstrap } from "commitizen/dist/cli/git-cz"
import path from "path"
export const runCommitCZ = () => {
const cliPath = path.join(__dirname, "../../../../node_modules/commitizen")…
-
Hey,
thanks for your work, this library is really useful :) While using it I had some improvement ideas :)
I think it will be great to prefill the changelog based on the commits before this rele…
-
Hi,
I noticed that CHANGELOG is not generated properly when I'm using my company's bitbucket server.
It would be nice to have a possibility to specify a template for generating e.g. `compare-chang…
-
I use Azure Devops for a python project. I've been using conventional commits for the lifetime of the project, so I liked the idea of standard-version.
When I run it, I get a CHANGELOG.md with inco…
-
## Expected Behavior
Each package will have a new package version correctly set based on the conventional commit history and previous package versions
## Current Behavior
All package versions are…
-
Hi,
I believe it's usually a good practice to to use this kind of commit message when making a new release:
```
chore(release): v0.4.2
```
And then tag this commit with `v0.4.2`. So it would be…
-
With multiple developers contributing, we should have some rules in place to ensure the `main` branch stays clean and tidy. I have some suggestions based on previous experience, very much open to disc…
-
As raised by @virkt25 in https://github.com/marionebl/commitlint/issues/75, there are use cases for multiple scopes in one commit (think mono repositories):
```
feat(pkg1, pkg2): add some new feat…