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?