Closed LeoColomb closed 2 years ago
@LeoColomb thank you for the issue, this makes sense to me :+1: do you have the correct perms on this repo to move forward with this?
regarding the src
branch: we can't create a release for that since it would appear as a published version to use on packagist, right? if so, i do think it's important that we backup that history to another repo prior to deleting
@retlehs Thanks for your reply!
you have the correct perms on this repo to move forward with this?
As soon as the branch protection rule is removed (I can't do that), yes I can.
regarding the
src
branch
You are right for packagist, ok for the backup.
@LeoColomb :+1:
src
branch history to be moved toBranches removed.
src
moved to https://github.com/roots/wordpress-generator-legacy, you can archive the repo if you want 😊
@LeoColomb thank you!
Terms
Summary
Currently the repo is hosting a lot of branches. The request/suggestion is to drop all these banches.
x.y.z-branch
ssrc
(shall we move to an archived repo?)nightly-svn
Exceptions(?):
nightly
(packagist report usage)nightly-git
(packagist report usage, very little though)Motivation
Why are we doing this?
Having all these branches "pollutes" a little the repo, making harder to find and maintain the relevant ones and could create confusion about tags. The new workflow won't publish branches anymore.
What use cases does it support?
That's the point, Packagist report exactly 0 download from these branches refs, with very few exceptions if we look at more than a year ago.
What is the expected outcome?
Lighter repo, easier to manage and support.
Potential conflicts / foreseeable issues
Well, this would delete content, so could eventually raise missing content errors. But will it?
Additional Context
Special case for
src
. Not used anymore, but contains previous code and it might be nice to move it to another repo for archive. Or not, if we don't care.cc @retlehs @swalkinshaw