codeowner havoc on stack submit
Offen
area/forge
enhancement
- Vorherrschende Sprache
- Go
- Sterne
- 762
- Forks
- 72
- Ø Merge
- 18 Std. 24 Min.
- Gemergte PRs (30 T.)
- 28
Beschreibung
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.
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.