My merged branches are often not being cleaned up ...
# report-bugs
t
My merged branches are often not being cleaned up by
gt sync -f
. No error message or anything, they just stick around. Maybe due to syncing and being “different” from remote even with no changes?
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>
t
I manually deleted so I don’t have any to show at the moment
p
Hey Tyler, interesting i have not seen previous reports of this. Few Qs for ya:
Maybe due to syncing and being “different” from remote even with no changes
can you elaborate on this? what would be different? Are they untracked?
I manually deleted
Are you manually deleting with
gt
? any pattern of the branches being all closed, or all merged, or is it a mix? And does Graphite UI show the correct status? I suspect not but, if you are able to reproduce would be great to get steps.
t
I’m using Graphite UI to see the branches and delete them. All were merged, not closed.
can you elaborate on this?
My hypothesis was that a previous
gt sync
without a corresponding
gt s
caused my local to “not match” the remote, even though the code was unchanged, just updating the base commit
They were all branches I hadn’t touched in a while. I submitted them then worked on other stuff (not stacked) while waiting for review
So I did
gt sync -f
multiple times before they were merged and didn’t resubmit the older ones since there were no conflicts