Release Notes: Ignore Issue Title if there are release notes written within a given ticket

[lsulak]

Background

Ignore Issue title if a given Issue has Release Notes in it. I find this to potentially improve the readability of our Releases - let's keep the information brief but detailed enough and tidy.

Or even better, make it configurable.

Example

Imagine that you have tickets 111 and 112, as detailed below.

Ticket 111 (author A1 worked on it)

Title: Implement Algorithm BFS for problem X

Release Notes

• BFS implemented for problem X
• Optimized the backend part Y by Z amount of % on average

Ticket 112 (author A2 worked on it)

Title: Enhancing Monitoring of the service Q

(and this ticket would have no release notes)

---

Final Release Draft would look like this:

...

New Features 🎉

• #110 - Introduce GH actions for version tag check and release notes presence #111 by @ A1

  • BFS implemented for problem X
  • Optimized the backend part Y by Z amount of % on average

• #57 - Configurable regex-based Release note detection in the PR body #112 Enhancing Monitoring of the service Q by @ A2

...

[benedeki]

I think the link to issue is additional data, not the key information.
I would like it like this:

• BFS implemented for problem X (#110 - Introduce GH actions for version tag check and release notes presence #111 by ...)
• Optimized the backend part Y by Z amount of % on average (#110 - Introduce GH actions for version tag check and release notes presence #111 by ...)

The #112 stays the same, just wapped order

[benedeki]

I even think the link to PR is completely surplus, just adds noise. The PR is linked in the issue. (Except warning chapter)

[benedeki]

Of course nest would be a possibillity to set it via a pattern with placeholders.
× placeholder for issue number

• placeholder for issue title
  × placeholder for PR number
  × placeholder for contributors
  × placehokder for release note comment one line
  × placeholder fir the whole release note comment
  × placeholder for date of item closing
  × maybe an escape character for placeholders
  × everything else are literals

[miroslavpojer]

Of course nest would be a possibillity to set it via a pattern with placeholders. × placeholder for issue number

• placeholder for issue title
  × placeholder for PR number
  × placeholder for contributors
  × placehokder for release note comment one line
  × placeholder fir the whole release note comment
  × placeholder for date of item closing
  × maybe an escape character for placeholders
  × everything else are literals

Do you mean some configurable GH Action input to manage 1st line in example below?

• '{Issue_number} {Issue_title} by {contributors}' ==> #110 - Introduce GH actions for version tag check and release notes presence #111 by @ A1
  • BFS implemented for problem X
  • Optimized the backend part Y by Z amount of % on average