Hey! We're currently setting up Graphite for our o...
# how-do-i
b
Hey! We're currently setting up Graphite for our open-source repository (github.com/hashintel/hash) and have some questions regarding approval workflows. To be able to merge a stack according to disable dismiss stale approvals (https://graphite.dev/docs/merge-pull-requests#compatibility-with-github-branch-protection-rules). The problem we are facing now is that this helps us merge the entire stack without unnecessary re-approval, but it also means that we have less security against unwanted changes, even from a non-malicious actor. If I have a PR approved but need to make some changes and forget to seek re-approval in the PR itself or in any upstream changes, the PR will still be marked as ready to be merged, which is undesirable (even if we are a trusted team). Is there any way to mitigate this problem?
p
(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
Hi Bilal, If you need non-rebase changes to be dismissed, we created an open-source GitHub Action that is a drop-in replacement for this rule. You can find it on the GitHub Actions marketplace here: https://github.com/marketplace/actions/dismiss-stale-approvals Docs ref
b
I think this is exactly what we’ve been looking for. Going to try it, thank you!