A coworker is having issue submitting his PR, he t...
# report-bugs
g
A coworker is having issue submitting his PR, he told me he deleted a branch which might have caused an issue. He did a sync, but now
gt submit
doesn't work and also the UI doesn't load the stack. Command executed:
gt submit --branch 10-09-file_cleanup --draft --force
ERROR received:
ERROR: Error response trying to pre-submit PRs: 500
Link to the last PR in the stack
p
(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>
g
tried doing
gt feedback
but getting
ERROR: Failed to report feedback, network response 500
also tried creating a new stack and that's working. So it seems to be an actual issue with that stack in particular, instead of an issue with the connection
p
Hey Guillermo, if hitting that 500 it may be a old cli. if they can update to 1.7.0 they should be able to submit via
gt feedback -d
see updating the CLI for instructions if needed.
g
now
gt feedback
worked, submitted the report
p
Ive got the logs and see the CLI version was updated Guillermo, thanks. have you tried running
gt restack
? also does the branch youre trying to submit exist in github?
g
yes, just tried running
gt restack
and the issue is still happening
the branch exists in github, is the link I sent before
we were able to 'solve' the issue going PR by PR in the stack submitting until one of them failed, and then folding that PR into the previous one
the stack in the UI is still not loading though
this is the
stackId
I saw in a network call
492d2def-7986-4b51-bb36-2559e019a1b4
p
Hey Guillermo, looks like this got resolved?
g
at the end we reviewed through github and merged the PRs one by one
p
Hey Guillermo, got it. Sorry you had to do these git gymnastics to get unstuck here.
g
no worries, just reporting in case there is something that could help it get fixed in the future