Introduce weak link between PR and Issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
The issue points to PR descriptions and GitHub’s default closing keywords as the starting points. Trace the existing keyword handling in the action, then verify that Relates #Nr links an issue without closing it after a merge, while the current closing keywords retain their behavior.
Written by the indexing model from the issue text.
Description
Background
In the current implementation, GitHub default keywords are used in the PR description to link the Issues.
All these keywords close the mentioned Issue when PR is merged.
Feature
Add similar keywords to link Issue(s) with PRs: Relates #Nr
This keyword will allow the team to link more partial or related PRs to one Issue without Closing after the first merge.
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 5
Getting set up
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
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openvinotoolkit/openvino_notebooks#3665 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
benchmark-gap
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day