feat: comment on issues and merge requests resolved by current release

[fgreinacher]

BREAKING CHANGE: By default all related issues and MRs are commented. Set the successComment option to false to disable that.

Fixes #40

🛠 with ❤ at Siemens

[fgreinacher]

OK, this is ready for review.

See https://gitlab.com/fgreinacher/semantic-release-comments/-/merge_requests/4 and its linked issues for a sample run from the current version of the this PR.

/cc @pvdlg @tmeijn @nfriend @joshdcomp as you have been active in the original issue.

[tmeijn]

@fgreinacher Awesome!

Two points of feedback I have:

1. The issue that the Merge Request closes does necessarily lives in the same project that the Merge Request is merged in. Looking at code, it does not account for that case.
2. Related to 1: the release is also not necessarily in the same project, so constructing a full url path should solve that case.

Thanks again!

[fgreinacher]

@fgreinacher Awesome!

Two points of feedback I have:

1. The issue that the Merge Request closes does necessarily lives in the same project that the Merge Request is merged in. Looking at code, it does not account for that case.
2. Related to 1: the release is also not necessarily in the same project, so constructing a full url path should solve that case.

Thanks again!

Good catch, thanks! I fixed this and also use the full release URL now.

[fgreinacher]

@semantic-release I am not sure who is currently maintaining this repository. Could you help me find the right reviewer?

[fgreinacher]

@travi Are you currently active here and would review this? 🙏

[github-actions]

🎉 This PR is included in version 7.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[fgreinacher]

@travi Eek, seems the squash commit did not contain my breaking change trailer, making this 7.1.0 instead of 8.0.0 :/ Should I revert this for 7.1.1 and recommit with the correct message?

[travi]

Yeah, that's the route that I would recommend. I've approved your draft PR for the revert.

I do wish that GitHub would do better with copying commit body details into the suggested squash message in situations like this.