You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I've got a queue of open contributions here that are all green/mergeable but haven't had a maintainer look at them yet, and I want to make sure I'm asking for review in the right place.
Current state (2026-09-08):
Ready for a merge decision — mergeable, bot-reviewed, no conflicts:
Web: make draft stashing discoverable in the composer
Notes for reviewers: every fix PR ships with focused tests, and each has had at least one independent automated review pass with findings triaged and addressed in-commit (receipts in the PR comments). Several fix the same underlying themes (V2 adapter lifecycle isolation, queued-turn persistence), so they may be easiest to review as a batch.
My question: since fork accounts can't set reviewer requests on upstream PRs, is pinging @juliusmarminge / @maria-rcks in PR comments the right way to ask for review here, or is there a channel/process you'd prefer? Happy to adapt — and if a couple of these are easy wins someone wants to grab, #10504, #10604, and #10607 are the smallest.
(There are also a few drafts in flight — mobile subscription widgets, task-completion motion, and a checkpoint/restart repair batch — I'll bring them here when their evidence gates are closed.)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi! I've got a queue of open contributions here that are all green/mergeable but haven't had a maintainer look at them yet, and I want to make sure I'm asking for review in the right place.
Current state (2026-09-08):
Ready for a merge decision — mergeable, bot-reviewed, no conflicts:
Mergeable, awaiting a first review pass:
Notes for reviewers: every fix PR ships with focused tests, and each has had at least one independent automated review pass with findings triaged and addressed in-commit (receipts in the PR comments). Several fix the same underlying themes (V2 adapter lifecycle isolation, queued-turn persistence), so they may be easiest to review as a batch.
My question: since fork accounts can't set reviewer requests on upstream PRs, is pinging @juliusmarminge / @maria-rcks in PR comments the right way to ask for review here, or is there a channel/process you'd prefer? Happy to adapt — and if a couple of these are easy wins someone wants to grab, #10504, #10604, and #10607 are the smallest.
(There are also a few drafts in flight — mobile subscription widgets, task-completion motion, and a checkpoint/restart repair batch — I'll bring them here when their evidence gates are closed.)
All reactions