Is there a way to sync a PR with main from Graphite's UI in a way that will not remove approvals?
We just started using https://github.com/withgraphite/dismiss-stale-approvals and it considers the "Update branch" button in github as a change which dismisses the approvals, but I don't see an alternative in Graphite UI for "update branch" - for context not all of our team members are comfortable with the CLI (e.g. QA)
p
Pylon
10/14/2025, 4:37 PM
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about:
- Screenshots / debug logs / list of commands you've tried to run so far
- Your workflow
- Current state
Pylon
10/14/2025, 5:53 PM
Hey Dorian, we do not currently have a way to handle this via the UI, but it been requested a few times so i can add you to the tracking ticket for that. The action you shared prevents dismissal on a rebase of the branch onto new main.
You should be able to perform this rebase instead of a merge commit in the "update branch" dropdown.
Pylon
10/14/2025, 5:57 PM
(ps that screenshot should have had the second option checked in case it was confusing)
d
Dorian Karter
10/14/2025, 6:26 PM
Thanks - we will try that!
Dorian Karter
10/14/2025, 6:27 PM
@Brett Bedevian I also asked another question via email about dismissal when base branch changes which is really annoying for stacked PRs where the base branch will always change.
p
Pylon
10/14/2025, 6:31 PM
alright, let me see if i can track that down, will respond in that thread-
d
Dorian Karter
10/29/2025, 2:25 PM
We tried the approach of using rebase, but that removes all signing from commits which are required.
So we had to stop using this workflow.
Unfortunately this makes stacked PRs pretty useless for us, because while they improve the ability to review in smaller chunks, they require re-reviews of the entire stack when a downstack PR is merged.
We have a requirement to have 2 people approve, which makes it really annoying to chase down people after each step is merged.