codeowner havoc on stack submit

[miclaraia]

Suppose we restack a stack and then submit changes to github with gs stack submit. This sometimes has a side-effect of many code-reviewers being auto-requested due to codeowner configurations in github.

I was wondering if it would be possible to avoid this by switching all PRs in a stack to/from draft mode before/after pushing changes as part of a stack submit? For example, on calling gs stack submit, I would want git-spice to switch all PRs in the stack to draft mode, proceed with stack submit as usual, and finally return all PRs back to their original draft/non-draft state.

[abhinav]

I've been aware of this problem and accepted that as a GitHub limitation.
I wasn't aware of this workaround.

switching all PRs in a stack to/from draft mode before/after pushing

If it works, it definitely makes sense to introduce as an experimental opt-in feature (initially), and make it opt-out down the line.
The implementation will have to be careful about the fact that not all GitHub repos/orgs are permitted to do draft PRs.