[GH-ISSUE #7720] [Workflow] Six contributions await human review; repeated upstream synchronization is costly #4624

New issue

Closed

opened 2026-10-31 00:51:32 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-31 00:51:32 +00:00

Owner

Originally created by @ShuaixinHuang on GitHub (Oct 28, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7720

Before submitting

I checked the related discussions and current PR review records.
This report contains no credentials, private samples or sensitive target data.

Six contributions still await an identified human reviewer

@morluto, could you please identify or assign reviewers for my six pending contributions: #7062, #7063, #7065, #7356, #7357 and #7730?

I rechecked their formal GitHub review records on October 28: all six remain open and none has a recorded human review. The first three were opened on October 25, #7356 and #7357 on October 27, and #7730 on October 28. Thank you for previously reviewing and merging my #7349; this request concerns these six remaining PRs.

Repeated upstream changes have required substantial conflict resolution, fixture alignment and validation while these contributions await a decision. I have spent much of my time repeating this maintenance rather than preparing further useful fixes. Some earlier contributions have also been superseded while pending, as documented in #7467. This ongoing cost is discouraging and makes it difficult to plan further contributions.

Requested action

Please help establish who will review each pending PR and provide an actionable decision: review, concrete requested changes, defer, or close if redundant or no longer useful. A clear owner and next step would reduce repeated synchronization and avoid maintaining changes that are no longer wanted.

I understand from #7243 that a reliable review date cannot be promised. I am asking for review ownership and a decision on the pending work. Automated checks and reviews do not substitute for that human review.

The earlier discussions (#7627, #7467 and #7488) remain open. The qualified contacts were already mentioned together in the existing comment below; this update keeps the request in one place. It requests no new runtime capability or target interaction.

Originally created by @ShuaixinHuang on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7720 ### Before submitting - [x] I checked the related discussions and current PR review records. - [x] This report contains no credentials, private samples or sensitive target data. ### Six contributions still await an identified human reviewer @morluto, could you please identify or assign reviewers for my six pending contributions: #7062, #7063, #7065, #7356, #7357 and #7730? I rechecked their formal GitHub review records on October 28: all six remain open and none has a recorded human review. The first three were opened on October 25, #7356 and #7357 on October 27, and #7730 on October 28. Thank you for previously reviewing and merging my #7349; this request concerns these six remaining PRs. Repeated upstream changes have required substantial conflict resolution, fixture alignment and validation while these contributions await a decision. I have spent much of my time repeating this maintenance rather than preparing further useful fixes. Some earlier contributions have also been superseded while pending, as documented in #7467. This ongoing cost is discouraging and makes it difficult to plan further contributions. ### Requested action Please help establish who will review each pending PR and provide an actionable decision: review, concrete requested changes, defer, or close if redundant or no longer useful. A clear owner and next step would reduce repeated synchronization and avoid maintaining changes that are no longer wanted. I understand from #7243 that a reliable review date cannot be promised. I am asking for review ownership and a decision on the pending work. Automated checks and reviews do not substitute for that human review. The earlier discussions (#7627, #7467 and #7488) remain open. The qualified contacts were already mentioned together in the existing comment below; this update keeps the request in one place. It requests no new runtime capability or target interaction.

bsakaguchi closed this issue

2026-10-31 00:51:32 +00:00

bsakaguchi commented

2026-10-31 00:51:33 +00:00

Author

Owner

@ShuaixinHuang commented on GitHub (Oct 28, 2026):

@morluto @gensokyo-dev @kaoru0822-kitauji @baron @N0zoM1z0 — could any of you with review or merge authority please review the five remaining PRs (#7062, #7063, #7065, #7356 and #7357), or help route them to an appropriate reviewer? Their latest required code CI, title and author-declaration checks have passed. Repeated upstream synchronization and revalidation have created substantial maintenance work. A review, requested-changes, defer or close decision would help me plan further focused contributions. Thank you for the review and merge of #7349. I cannot access the complete collaborator permission list, so please correct or redirect this request if needed.

@ShuaixinHuang commented on GitHub (Oct 28, 2026): @morluto @gensokyo-dev @kaoru0822-kitauji @baron @N0zoM1z0 — could any of you with review or merge authority please review the five remaining PRs (#7062, #7063, #7065, #7356 and #7357), or help route them to an appropriate reviewer? Their latest required code CI, title and author-declaration checks have passed. Repeated upstream synchronization and revalidation have created substantial maintenance work. A review, requested-changes, defer or close decision would help me plan further focused contributions. Thank you for the review and merge of #7349. I cannot access the complete collaborator permission list, so please correct or redirect this request if needed.

bsakaguchi commented

2026-10-31 00:51:33 +00:00

Author

Owner

@morluto commented on GitHub (Oct 28, 2026):

I appreciate your work a lot. But please stop opening issues just to track your own PRs.

@morluto commented on GitHub (Oct 28, 2026): I appreciate your work a lot. But please stop opening issues just to track your own PRs.

bsakaguchi referenced this issue

2026-10-31 01:13:44 +00:00

[PR #4651] [CLOSED] docs(cli): list Kuna as a doctor provider #6344

bsakaguchi referenced this issue

2026-10-31 01:14:10 +00:00

[PR #4767] [MERGED] docs(installation): list every engine accepted by doctor --provider #6400

bsakaguchi referenced this issue

2026-11-01 21:42:31 +00:00

[PR #4992] [CLOSED] docs: include Kuna in the doctor provider list #6715

bsakaguchi referenced this issue

2026-11-01 21:42:38 +00:00

[PR #5011] [MERGED] docs(cli): include Kuna in supported doctor providers (#4624) #6731