Katya Pavlenko
Katya Pavlenko
got same error on node v12.4.0, downgrading to 1.2.2 helped
Hi, I'm having alike issues now, sometimes my merge commit is ingnored, sometimes not I believe it's related to command `git log -- ` being used, which uses [simplified history](https://stackoverflow.com/questions/56553346/git-log-missing-merge-commit-that-undid-a-change)
+1, much needed for monorepos
faced same issue https://github.com/conventional-changelog/conventional-changelog/issues/924
@rajput2017 which behavior you'd prefer? not to put tags on commits which already exist in master?
@rajput2107 but no commits are modified, it's the beauty of tags
@rajput2107 sorry, I did not get your question `why we can't include other tags on the last commit of that branch too`, can you elaborate?
Are you sure package.lock is needed to be in repo?
What is the difference between my PR and your except of changes in `Mock.ts`?
@bendykowski okey, now I see the difference, thank you. Your solution looks better The only one thing you forgot is `toString`, method for `not() .` matcher, I think it might...