HippoBaro commented on PR #11273: URL: https://github.com/apache/arrow-rs/pull/11273#issuecomment-6591138439
@alamb I’m happy to report that all of "Stack A" has now merged upstream! That was the easier part, since those commits were mostly independent bug fixes and small refactors laying the groundwork for the larger changes that follow. As we discussed, I was planning to submit the next stack as [native stacked GitHub PRs](https://docs.github.com/en/pull-requests/reference/stacked-pull-requests). Unfortunately, I hadn’t accounted for one limitation: all branches in a native stack, including its target branch, **must live in the same repository**. That's a bummer, and means I can’t use this workflow to target upstream while hosting the branches on my fork. Would it be possible to arrange for the stack’s branches to be hosted in `apache/arrow-rs`? If granting me the access needed to push those branches is an option, I’d be happy to follow whatever conventions or restrictions you prefer (I wouldn't need access to `main`.) I think a native stack would give reviewers the best experience: each commit would have a focused diff, while its place in the overall design would remain visible. The commits are individually correct and tested, so submitting them one at a time is possible; my concern is that reviewing them in isolation would make the broader architectural changes harder to follow. If hosting the branches upstream isn’t practical, I’m very happy to find another approach together! Thanks again for all your help getting this upstream 🙇 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
