[GH-ISSUE #7762] [Workflow] Six pending contributions need human reviewers; repeated upstream synchronization is costly #4634

Closed
opened 2026-10-31 00:51:38 +00:00 by bsakaguchi · 2 comments
Owner

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

Current contribution tracking — October 28

Please assign reviewers and provide a clear next step for the open contributions below.

I was concerned that older PRs had become difficult to find, so I resubmitted #7062 as #7779, #7063 as #7781 and #7065 as #7780. The original three were opened on October 25. The replacement PRs were opened on October 28, with refreshed, focused diffs and links preserving the old discussions and evidence.

The October 27 contributions were also refreshed and resubmitted: #7356 is replaced by #7785 (XML), and #7357 by #7786 (scenario MIME). Both original PRs are now closed with replacement links. These are the same contributions, not additional independent work.

Open PR Latest head Required code CI Status
#7779 1a1dc1dc Success Open
#7780 ba3f4f90 Success Open
#7785 0fa80e09 Pending Replaces #7356; new-head CI must complete.
#7786 a709e628 Pending Replaces #7357; new-head CI must complete.

Merged and complete: #7781, #7730, #7764.

CI labels above refer to each listed head at this update. Pending checks are not passing results; earlier green heads do not validate replacement heads. Each PR retains its actual evidence and local verification limitations.

Review ownership and maintenance cost

Repeated upstream changes have required conflict resolution, fixture alignment and validation while contributions await a decision. Please identify a reviewer and give an actionable decision for each remaining PR: review, concrete requested changes, defer, or close if redundant. Clear ownership will reduce repeated maintenance and help me continue contributing useful fixes.

Context and original reports remain in #7720, #7627, #7467 and #7243. Please use this tracking issue for a consolidated response.

Originally created by @ShuaixinHuang on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7762 ### Current contribution tracking — October 28 Please assign reviewers and provide a clear next step for the open contributions below. I was concerned that older PRs had become difficult to find, so I resubmitted #7062 as #7779, #7063 as #7781 and #7065 as #7780. The original three were opened on October 25. The replacement PRs were opened on October 28, with refreshed, focused diffs and links preserving the old discussions and evidence. The October 27 contributions were also refreshed and resubmitted: #7356 is replaced by #7785 (XML), and #7357 by #7786 (scenario MIME). Both original PRs are now closed with replacement links. These are the same contributions, not additional independent work. | Open PR | Latest head | Required code CI | Status | | --- | --- | --- | --- | | #7779 | `1a1dc1dc` | Success | Open | | #7780 | `ba3f4f90` | Success | Open | | #7785 | `0fa80e09` | Pending | Replaces #7356; new-head CI must complete. | | #7786 | `a709e628` | Pending | Replaces #7357; new-head CI must complete. | Merged and complete: #7781, #7730, #7764. CI labels above refer to each listed head at this update. Pending checks are not passing results; earlier green heads do not validate replacement heads. Each PR retains its actual evidence and local verification limitations. ### Review ownership and maintenance cost Repeated upstream changes have required conflict resolution, fixture alignment and validation while contributions await a decision. Please identify a reviewer and give an actionable decision for each remaining PR: review, concrete requested changes, defer, or close if redundant. Clear ownership will reduce repeated maintenance and help me continue contributing useful fixes. Context and original reports remain in #7720, #7627, #7467 and #7243. Please use this tracking issue for a consolidated response.
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.

<!-- gh-comment-id:6468272750 --> @morluto commented on GitHub (Oct 28, 2026): I appreciate your work a lot. But please stop opening issues just to track your own PRs.
Author
Owner

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

Thank you for your kind words, and for reviewing and merging my contributions. I appreciate your help.

I am sorry for opening repeated issues. With several PRs accumulating, repeated upstream synchronization, conflict resolution and validation became a substantial maintenance burden, and I became anxious about spending more time keeping pending work current than contributing new fixes. That is why I followed up so insistently.

I understand your request and will stop opening issues just to track my PRs. I will keep future technical updates and review follow-ups in the relevant PRs. Thank you again for your time and support.

<!-- gh-comment-id:6468377238 --> @ShuaixinHuang commented on GitHub (Oct 28, 2026): Thank you for your kind words, and for reviewing and merging my contributions. I appreciate your help. I am sorry for opening repeated issues. With several PRs accumulating, repeated upstream synchronization, conflict resolution and validation became a substantial maintenance burden, and I became anxious about spending more time keeping pending work current than contributing new fixes. That is why I followed up so insistently. I understand your request and will stop opening issues just to track my PRs. I will keep future technical updates and review follow-ups in the relevant PRs. Thank you again for your time and support.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#4634
No description provided.