General feedback after first use

[kevinwallimann]

• Chapter "Issues without Release notes" is not necessary imo. Sometimes you don’t need release notes and if they are really missing you will see it in the release draft, because the release notes are just not there. All of the issues in that chapter will be duplicates, so you always have to remove them.
• I would omit chapters if “No entries detected” -> Unnecessary deletion effort. Deletion is not free, you always have to double-check that you don’t delete something inadvertently
• PRs without linked issue: Would be nice if they could be handled more gracefully, as a first-level citizen like an issue. Sometimes it doesn’t make sense to have an issue for a PRs, e.g. for bug fixes. Also for open-source contributions we can probably not mandate that an issue be created for each PR.
• Maybe related: Closed PRs (as opposed to merged PRs) can probably also be omitted. Arguably they are rare, but I can't think of a scenario where a closed PR should still be in the release notes. But just my point of view.

[miroslavpojer]

Chapter "Issues without Release notes" is not necessary imo. Sometimes you don’t need release notes and if they are really missing you will see it in the release draft, because the release notes are just not there. All of the issues in that chapter will be duplicates, so you always have to remove them.

This chapter still could provide useful information when the presence of Release notes is required by project rules.
Here is a planned issue to add skip logic into action. With this improvement, the team can mark Issues without Release notes comments by intention.

[miroslavpojer]

I would omit chapters if “No entries detected” -> Unnecessary deletion effort. Deletion is not free, you always have to double-check that you don’t delete something inadvertently

I have created a new feature issue to address this idea.

[miroslavpojer]

Maybe related: Closed PRs (as opposed to merged PRs) can probably also be omitted. Arguably they are rare, but I can't think of a scenario where a closed PR should still be in the release notes. But just my point of view.

You have identified the not covered area. Thanks

The main idea of this GH action is to provide the "Final check". It is the default setting too.
See issue

[miroslavpojer]

PRs without linked issue: Would be nice if they could be handled more gracefully, as a first-level citizen like an issue. Sometimes it doesn’t make sense to have an issue for a PRs, e.g. for bug fixes. Also for open-source contributions we can probably not mandate that an issue be created for each PR.

Do you have some suggestions for change here?

Update:
After call I have created new issue

[miroslavpojer]

Issue solved.