Add release notes as comments

Would be nice if the extension allowed to save release notes of the dependencies as PR comments. I see 2 advantages of the switch:

1. Work items wouldn’t automatically be mentioned by the merge commit. If the release note contains Azure’s #1234 ticket linking syntax, the accidentally mentioned ticket number could conflict with other automations, like Work Item Updater or the built-in auto-close feature.
2. When updating by multiple versions, it could allow seperate validation of the changes comment-by-comment. Commit description could still be explicitly edited.

My pain point is 1. and I’m open to other suggestions and to help with the implementation.

[mburumaxwell]

For the tools to not be linked to work items, I believe you would need to change the logic for generating the description to strip out special character sequences. It is easier than writing the changes in comments. Unfortunately, I do not have the time to do this but you can give it a shot.

[hbendev]

Thanks for your time and the details, however, I have a custom automation set up that modifies tasks in a custom pipeline, and I’m not using the built-in functionality to close them automatically. This process picks up the tasks linked to the pipeline itself:

---

The work items can get linked multiple ways AFAIK, but what I want to avoid when using debendabot is to have no extra work item referenced accidentally. If the release notes contain a link to an issue/pr on github (for example:

7d39c2c Token cache optimization (#5806)

then, the issue #5806 from my own project might be mentioned in the merge commit, if I forget to change the PR’s description.

Sorry for not being clear enough.