With a PR chain, when

gt submit

triggers a GitHub rate limit all the PRs, all PRs on top of the last one successfully submitted end up with an incorrect parent (I guess the old one) and it is not possible to recover by doing a re-submit. a manual restacking with conflict resolution has to be done PR by PR. I know the PR chain is a bit big, but there should be an easy way to recover from this state. Thanks

gt submit --cli
🥞 Validating that this Graphite stack is ready to submit...

📝 Preparing to submit PRs for the following branches...
▸ TD-1069 (Update code)
▸ TD-1076 (Update code)
▸ TD-1077 (Update code)
▸ TD-1078 (Update code)
▸ TD-1079 (Update code)
▸ TD-1080 (Update code)
▸ TD-1081 (Update code)
▸ TD-1084 (Update code)
▸ TD-1086 (Update code)
▸ TD-1095 (Update code)
▸ TD-1096 (Update code)
▸ TD-1112 (Update code)
▸ TD-1100 (Update code)
▸ TD-1109 (Update code)
▸ TD-1110 (Update code)
▸ TD-1111 (Update code)
▸ TD-1116 (Update code)
▸ TD-1117 (Update code)
▸ TD-1122 (Update code)
▸ TD-1123 (Update code)
▸ TD-1125 (Update code)
▸ TD-1134 (Update code)
▸ TD-1130 (Update code)
▸ TD-1131 (Update code)
▸ TD-1132 (Update code)
▸ TD-1133 (Update code)
▸ TD-1136 (Update code)
▸ TD-1137 (Update code)

🚀 Pushing branches to remote...
Running git push: [========================================] 100% | Done

📨 Creating/updating PRs...
TD-1069: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/954> (updated)
TD-1076: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/961> (updated)
TD-1077: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/962> (updated)
TD-1078: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/963> (updated)
TD-1079: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/964> (updated)
TD-1080: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/965> (updated)
TD-1081: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/967> (updated)
TD-1084: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/969> (updated)
TD-1086: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/970> (updated)
TD-1095: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/980> (updated)
TD-1096: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/981> (updated)
TD-1112: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/991> (updated)
TD-1100: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/987> (updated)
TD-1109: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/988> (updated)
TD-1110: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/989> (updated)
TD-1111: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/990> (updated)
TD-1116: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/995> (updated)
TD-1117: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/996> (updated)
TD-1122: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/1000> (updated)
TD-1123: <https://app.graphite.com/github/pr/tabsdata/tabsdata-os/1001> (updated)
ERROR: Failed to submit PR for TD-1125:
Looks like you've triggered a GitHub API secondary rate limit 🥞 Nice stack!
Please wait a moment and then try your submit operation again.

(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using

gt feedback --with-debug-context <any message>

hi brett, we already reconciled things by hand from the github PRs. it was kind of painful. 2nd time it happens to us.