Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#40 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
release, tooling

Research direction

Start by finding where the action parses issue bodies for Release Notes and where it formats each issue into the final release draft. Use the examples in the issue as the expected behavior: tickets with release notes should omit the issue title, while tickets without release notes should keep it. The configurable option is mentioned but not specified, so confirm scope before implementing.

Written by the indexing model from the issue text.

Description

enhancement

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 🎉
  • #111 by @ A1

    • BFS implemented for problem X
    • Optimized the backend part Y by Z amount of % on average
  • #112 Enhancing Monitoring of the service Q by @ A2

...

Dominant language
Python
Stars
13
Forks
0
Avg merge
1m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AbsaOSS/generate-release-notes

All issues in AbsaOSS/generate-release-notes

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.