git remote prune origin
Worked great thank you.
On Oct 13, 5:38 am, Artiom Diomin wrote:
> В Пнд, 12/10/2009 в 10:23 -0700, donnoman пишет:
>
> > Our team creates topic branches, then when they are ready rebases them
> > and merges them into our testing branch and then deletes the old topic
> >
For your question, if there are a lot of branches involved, your best
bet is probably to write a quick script which runs through the
branches on origin deleting the local copies, and recreating them from
origin (or if you're daring, using update-ref to directly move them to
the proper location).
They are remote tracking, we create them as remotes for code review
and testing. Once we are satisfied we rebase and merge to testing,
then delete the remote tracking branch so the I'll effects of history
rewriting are never present.
The side effect is that the deletion of that origin only
В Пнд, 12/10/2009 в 10:23 -0700, donnoman пишет:
> Our team creates topic branches, then when they are ready rebases them
> and merges them into our testing branch and then deletes the old topic
> branch.
>
> Apparently git pull and fetch don't automatically trim the list of
> branches that it thi
On 12/10/09 donnoman said:
> Our team creates topic branches, then when they are ready rebases them
> and merges them into our testing branch and then deletes the old topic
> branch.
>
> Apparently git pull and fetch don't automatically trim the list of
> branches that it thinks origin has.
>
>
