This message was deleted.

a “really long time” being like 3-4 seconds

We currently do a questionably necessary check here at the git level when we could just be checking the PR's merged status. The longer each branch is and the further behind trunk it is, the longer this check takes. I've considered removing it and I've also thought about caching it. With that said — for now, you can look at the

--debug

output to see which branch might be taking so much time as it'll have a lot of

merge-base

and

cherry

calls traversing its history, and likely untrack it as a workaround — I imagine that if it's not being rebased, you likely don't need it tracked.

cool, that sounds like the issue. I have a few very old branches that havent been rebased due to conflicts which ive been too lazy to delete

so we also at this point in the command make a network call to ensure the PR statuses are up to date

theres a request I see in the logs that looks like:

yeah, it should only be tracked branches

hmnm, it does seem like those branches still exist locally but im not sure if theyre tracked

ah, that might be the issue then. i'll make sure we only include tracked branches in the query

so basically this request is asking the graphite API for the status of the PRs for these branches?

yes

also not sure if this is relevant but generally we dont actually use graphite to manage our PRs and still go through github for merges

thats fine, we pass through to github

cool. yeah so then I think its just a case of having switched to graphite after a year or so of this repo, meaning i have hundreds of old branches laying around