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

Merge PR and issue labels when considering release notes group

Open
  • Is something wrong?
#96 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the release-note grouping logic and its existing label handling, then inspect how labels are read from the RN and the issue. Check cases where labels exist on either or both sources; done means the release-note group reflects labels from both. The issue names no files or tests, so first find the relevant entry point and test coverage.

Written by the indexing model from the issue text.

Description

enhancement

Background

Sometimes, the important labels are placed on PR, sometimes on issue

Feature

When considering labels, take into account both the RN and issue

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.