[GH-ISSUE #7627] [Workflow] Multi-day review delays and repeated upstream conflicts are creating substantial maintenance costs #4554

New issue

Open

opened 2026-10-31 00:50:43 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:50:43 +00:00

Owner

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

Before submitting

I searched related open and closed discussions, including #7243, #7467 and #7488.
This request contains no credentials, private samples or sensitive target data.

Review request and maintenance impact

@morluto, thank you for reviewing and merging #7349. I am sorry that I did not notice some earlier upstream conflicts promptly enough.

I am following up on the five remaining PRs because repeated upstream changes while they await a review decision are creating substantial maintenance costs. On October 27, I spent much of the day resolving overlaps, updating the same branches and repeating validation. This cycle takes time away from preparing further useful contributions and is becoming difficult to sustain.

The older three PRs, #7062, #7063 and #7065, were opened on October 25 and are now in their fourth calendar day, October 28. #7356 and #7357 were opened on October 27. I would appreciate timely review and a concrete next step for each, rather than repeatedly synchronizing them while the review outcome remains uncertain.

Current verification

Checked immediately before this report: all five current heads have successful required code CI, title checks and human author-declaration checks. GitHub reports no merge conflicts.

PR	Current head	Required code CI
#7062	`7fd6b231`	success
#7063	`133136f8`	success
#7065	`30b16ef5`	success
#7356	`c587807f`	success
#7357	`c37ba3e2`	success

Requested outcome

Could you please help prioritize these ready contributions for review and give a merge, requested-changes, defer or close decision? If a PR is redundant or no longer useful, please feel free to close it or say which part should be dropped. A clear decision would reduce repeated conflict resolution and revalidation, and help me plan the additional fixes I want to contribute.

I understand your reply in #7243 that a reliable review date cannot be promised and that CI success does not replace final maintainer review. This follow-up emphasizes the ongoing maintenance cost and asks for actionable decisions on the remaining contributions. The earlier issues remain open for their existing discussion.

Target interaction

No target interaction; contribution workflow only.

Originally created by @ShuaixinHuang on GitHub (Oct 27, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7627 ### Before submitting - [x] I searched related open and closed discussions, including #7243, #7467 and #7488. - [x] This request contains no credentials, private samples or sensitive target data. ### Review request and maintenance impact @morluto, thank you for reviewing and merging #7349. I am sorry that I did not notice some earlier upstream conflicts promptly enough. I am following up on the five remaining PRs because repeated upstream changes while they await a review decision are creating substantial maintenance costs. On October 27, I spent much of the day resolving overlaps, updating the same branches and repeating validation. This cycle takes time away from preparing further useful contributions and is becoming difficult to sustain. The older three PRs, #7062, #7063 and #7065, were opened on October 25 and are now in their fourth calendar day, October 28. #7356 and #7357 were opened on October 27. I would appreciate timely review and a concrete next step for each, rather than repeatedly synchronizing them while the review outcome remains uncertain. ### Current verification Checked immediately before this report: all five current heads have successful required code CI, title checks and human author-declaration checks. GitHub reports no merge conflicts. | PR | Current head | Required code CI | | --- | --- | --- | | #7062 | `7fd6b231` | [success](https://github.com/morluto/rea/actions/runs/40518816354) | | #7063 | `133136f8` | [success](https://github.com/morluto/rea/actions/runs/40519805150) | | #7065 | `30b16ef5` | [success](https://github.com/morluto/rea/actions/runs/40519933659) | | #7356 | `c587807f` | [success](https://github.com/morluto/rea/actions/runs/40520393304) | | #7357 | `c37ba3e2` | [success](https://github.com/morluto/rea/actions/runs/40520561853) | ### Requested outcome Could you please help prioritize these ready contributions for review and give a merge, requested-changes, defer or close decision? If a PR is redundant or no longer useful, please feel free to close it or say which part should be dropped. A clear decision would reduce repeated conflict resolution and revalidation, and help me plan the additional fixes I want to contribute. I understand your reply in #7243 that a reliable review date cannot be promised and that CI success does not replace final maintainer review. This follow-up emphasizes the ongoing maintenance cost and asks for actionable decisions on the remaining contributions. The earlier issues remain open for their existing discussion. ### Target interaction No target interaction; contribution workflow only.

bsakaguchi referenced this issue

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

[PR #4554] feat(browser-extension): inspect declared CRX and XPI manifest surfaces #6305

bsakaguchi referenced this issue

2026-11-01 21:11:07 +00:00

[GH-ISSUE #5654] [Tracker] Open PRs that can't merge yet: conflicts and red CI (October 2026) #3425

bsakaguchi referenced this issue

2026-11-01 21:43:15 +00:00

[PR #5213] test(mcp): normalize server identity fixture paths on Windows #6818