[ckan-dev] Cleaning up old branches

[Toby Dacre]

On 28 February 2013 15:27, Vitor Baptista <vitor at vitorbaptista.com> wrote:
> Hi,
>
> As we use feature branching in our day-to-day workflow, we end up with lots
> of branches (482 so far). Some (lots?) are useful, but many are just
> garbage. Mainly code that's already merged into master. The command:
>
>> git branch -r --merged
>
>
> gives me 287 branches that are already merged into master (I ignored
> release*, stable and ultrastable). They should be safe to delete.

The clean the old branches is a long held dream

I think we should delete all the merged  bug-..., feature-...,
enhancement-.. ones as they will be quite old what do others think

but yes we should try to keep stuff clean
>
> I agree that this is not that important, and that it might be safer to leave
> it as is. Maybe remove them some time in the future. What I would like to
> ask is only that, whoever merges a pull request, please also delete its
> branch.
>
> Cheers,
> Vítor.
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>