RE: Suggested github housekeeping - stale branches

Not that it will help you with the stale branches you have, but you can get an admin to set github to automatically delete the branch after a pull request is merged. We've done that for a number of the publishing repositories to help cut down this maintenance nuisance.

For reference: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches

Matt

-----Original Message-----
From: Patrick H. Lauke <redux@splintered.co.uk> 
Sent: Friday, July 14, 2023 12:35 PM
To: w3c-wai-gl@w3.org
Subject: Re: Suggested github housekeeping - stale branches

Just a reminder about this...I still see we have branches hanging about that are 5-7 years old. I would hazard a guess that stuff in those branches has either been dealt with (merged into main?) or just not relevant anymore. It's a thankless task (I did do a little bit of housekeeping on this a few years ago, trying to find branches that were clearly left over from successful merges) for sure, but ... it would really help with just being able to concentrate on the things that are still active/being worked on.

On 15/09/2021 23:47, Patrick H. Lauke wrote:
> There are currently 297 branches on WCAG in github. A very large 
> number of them stale, as they have either been closed, merged, or lay 
> dormant and untouched for years.
> 
> https://github.com/w3c/wcag/branches/stale
> 
> Could I suggest deleting the ones that are merged/closed? And 
> probably, as part of the merging process, deleting the related 
> branches after merging?
> 
> P

--
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux https://mastodon.social/@patrick_h_lauke | skype: patrick_h_lauke

Received on Monday, 17 July 2023 17:57:47 UTC