Feature request: Inheriting closing issues from sub-PRs

[ufukty]

Select Topic Area

General

Body

Context

Sometimes I prefer opening additional branches from a feature branch for implementing multi-commit changes and introducing with a --no-ff merge. Working with nested PRs leave a commit history that is nicely organized and easily digestible.

Problem

Closing the resolved issues manually after each PR is manageable but redundant. Especially becomes annoying where the issue hierarchy between sub and sup issues have some depth and breadth.

Real example

This issue is not marked as closed after neither the resolving PR merged titles branch meta nor the following PR merged meta to main and keeping other blocked issues open. It looks like PRs don’t inherit the resolving issue information from PRs of branch commits. As a turnaround I can manually copy the closing keyword containing text to the super-PR prior merging, or in this case manually marked the issues as closed.

Suggestion

I suggest revamping the "closing keyword" functionality of PRs for adding inheritance-like mechanism between nested PRs. Whenever a branch previously has a PR with closing issues has been merged to main branch with another PR, the set of inherited issues should also be processed as they are directly linked in the super PR.

Related

I could not find an exact feature request in repository. Although some within the perimeter:

• [Feature Request] Prevent issues from being closed by merging linked PRs #23476 suggests more control over the auto closing behavior while appreciating the issue-PR linking for information convenience doesn't conflict with inheriting linked issues from nested PRs for information as long as the user provided with option of auto-closing behavior.
• Sub-issue cannot be closed via closing keywords #178149 mentions a propagation issue from sub-issues to sup-issues hints the expectation of improving user experience through eliminating redundant interactions through automation.