This message was deleted.

i'm actively working on comment speed, but you're right that there is a floor to how fast we can make it on the server-side

Heck yeah!

yep! we do it in the app in general, but for the commenting feature it's a (current) gap

exactly

it's possible we need to submit in a sequential order (e.g we don't want to just parallel submit them all, especially if you've changed the ordering of the stack), but i'm not sure

great questions

to double check, were you aware of the

gt branch submit

command (you can submit the current branch only and save the others for later)?

TIL! however I do like to push up everything so that my local == remote

and i'm also curious what you feel blocked on while the submit happens?

e.g. could you just kick it off and switch to a different terminal pane/tab

or is there something you're waiting on explicitly there?

Nope, wasn't feeling blocked. So in that sense, this is not a high-prio issue, it seems like I could keep working, even check out another branch and it didn't seem to interrupt the process. So this is not a big deal actually – compared to the PR comment thing, where I have to watch and wait for the PR comment to post because I want to make sure it's posted (especially if I write a Ulysses). Though for the comment thing, if it was optimistically updated, I would feel comfortable moving on without waiting for it to be confirmed posted in some way if it displayed some sort of error to me if it failed.

that all makes sense thanks