We’re keen to use stacked PRs at work.
We’re using agentic coding heavily, but still reviewing code to help us steer the software architecture and keep our understanding of the implementation. We generate large changes quickly, but need to break them into smaller, logically ordered PRs for review.
It’s nice for the reviewer to be able to look ahead through the full change, so they see can check the big picture, rather than merging a couple of PRs and then spotting that the abstractions are wrong.
PR stacks work very well for providing this kind of visibility, but are annoying to merge. After one PR in the stack is merged, the next PR needs to be rebased onto and targeted to the updated main branch. With our branch protection rules, this triggers another CI run and dismisses the PR approval, requiring human intervention.
It would be much nicer to have the reviewer go through all the PRs and then merge the stack in one go.
I struggle with this too.
At the moment I have a huge list of filtered keywords to exclude certain topics or words likely to appear in extreme content. It does cut out a lot of content that I don’t want to see, but doesn’t help with general negativity and doesn’t work with image posts.
I’m thinking of setting up my own filtering system with sentiment analysis, OCR and image classification so I can make my feed more balanced.