Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119138
Message-ID: <e8c2c35d-bd57-fa2c-b9d9-aaf3d509115b@bastelstu.be>
Date: Tue, 13 Dec 2022 19:03:40 +0100
MIME-Version: 1.0
Content-Language: en-US
To: Sara Golemon <pollita@php.net>,
 =?UTF-8?B?TWljaGFlbCBWb8WZw63FoWVrIC0gxIxWVVQgRkpGSQ==?=
 <vorismi3@fjfi.cvut.cz>
Cc: internals@lists.php.net
References: <4c1e58ca94c3069b8704b7068254fe3926c5ad17ab62bf88bfed79de0c62bd10@mahalux.com>
 <CAESVnVoVCkGYtgoYFkA=qNSupo7bDeXEYCyo3VZEKUKWPHYHcw@mail.gmail.com>
In-Reply-To: <CAESVnVoVCkGYtgoYFkA=qNSupo7bDeXEYCyo3VZEKUKWPHYHcw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Remove PHP-x.y.* git branches
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=)

Hi

On 12/13/22 18:55, Sara Golemon wrote:
> Why do you want to remove these branches?
> 
> I agree that they have minimal value especially since the tags are the
> actual release commit (and for release process versions often represent a
> spur off the release branch), but the cost in the repo is negligible.  What
> is gained from removing information from the repository?

One benefit of removing those branches would be, that usability of 
GitHub's branch selector improves, specifically the branch selector when 
creating a new PR.

Currently one needs to know the exact naming scheme and then use the 
"Find a branch" input to efficiently find a specific target branch. With 
the extra branches removed, one can open the dropdown and simply click 
the correct branch without needing to think.

Best regards
Tim Düsterhus