PR–Issue Linking & Label Intelligence (v1.5.0)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the umbrella design issue #228, then review subtasks #79, #96, and #40 to understand the separate association and release-note requirements. Done means weak links work when explicit links are absent, PR and issue labels are merged, issue-body release notes can replace titles, and existing explicit-link behavior remains compatible.
Written by the indexing model from the issue text.
Description
Background
The association model between pull requests and issues is a core engine of the action. Currently, linking relies on explicit references only, and label resolution does not consider both entities together. This leads to PRs or issues being misclassified in the generated release notes.
This epic improves the PR–Issue association model with a weak-link mechanism, merges label logic across both entities, and enables the tool to use rich issue-body release notes in place of issue titles.
Goals
- Introduce a flexible, improved PR–Issue linking and association model (#228)
- Implement weak (heuristic) linking between PRs and Issues when explicit links are absent (#79)
- Merge PR and issue labels when determining the release notes group for an entry (#96)
- Allow ignoring the issue title when explicit release notes are provided inside the issue body (#40)
- Maintain backward compatibility with existing explicit-link behaviour
Subtasks
- #228 Feature: Improved PR-Issue Linking and Association Model
- #79 Introduce weak link between PR and Issue
- #96 Merge PR and issue labels when considering release notes group
- #40 Release Notes: Ignore Issue Title if there are release notes written within a given ticket
Related / References
- #228 is the umbrella design issue for this epic
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- Avg merge
- 6h 50m
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbsaOSS/generate-release-notes
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
epic
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in AbsaOSS/generate-release-notes
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100