Hutson Betts

@tebriel, is additional outside testing of the v2.0 branch needed before release?

@conventional-changelog/conventional-changelog thoughts on this change? Seems reasonable to me.

@myii and @joelmukuthu do y'all have a small example project, and release explanation, that we can use to reproduce this issue? It was really help us to better investigate this...

My two cents would be to simply document what `git` already does. As noted by @damianopetrungaro using `git revert` and keeping it's auto-generated message is easy. Doing anything else just...

> partial revert Thank you @Mouvedia for the link. I was failing to see that you are reverting only part of a commit and not the entire commit. > So...

> @hbetts what about other commit types like docs/chore? If I introduce documentation that is inaccurate, I tend to revert the commit, use the `docs` type, along with a description...

> We are **_inspired_** by the Angular convention, **_we are not following it_**. :wink: @damianopetrungaro do you feel we should be inspired in a different direction than the standard Angular...

I agree with @stevemao's naming suggestion. Though, we should probably figure out how to share commit types, and other commit message conventions, between `conventional-changelog` presets (used for parsing commits and...

We encountered a similar issue within our GitHub Enterprise Server deployment (Which uses self-hosted runners). We're currently running GitHub Enterprise Server 3.3, but our repositories are receiving automated PRs to...

:+1: Coverage integrated into the Releases page would be fantastic!