ignore reverted commits

[chingor13]

If we merge a feature, but then revert it, before the next release, we should be able to ignore the original PR from both the release history and the rules for version bumping.

[bcoe]

@chingor13 the idea I had for this was that we could add a footer message with the sha that was reverted perhaps?

reverts: revert the feature foo

Revert: abc123 (the foo feature commit sha)

[peblair]

I know this is an old issue, but this feature would be quite useful! Even if it required manually specifying the Revert: <sha> commit as described by @bcoe, it would be great if it were possible to have this behavior without having to modify the changelog (or rewriting git history), as mistakes happen!

[moltar]

Would be great to be able to parse and/or ignore reverts.

Even when following Conventional Commits, sometimes doing a click & revert in GH is common, and it leaves by default the following commit format:

Revert "fix(deps): update dependency foobar to v4" (#3855)

I think since could be such a common case due to GitHub ubiqutousness, it'd be great to support this special case.

Otherwise, Release Please warns with the following log entry:

❯ commit could not be parsed: 4100f18cf17df44f10aef3c4796f0b7d7c45d827 Revert "fix(deps): update foo to v4" (#3855)

[jolars]

This is supported in https://github.com/semantic-release/semantic-release. Maybe we could borrow from there?

[jolars]

I ended up making my own package inspired by release please: https://versionary.dev which handles this.