You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've never really liked the name and would prefer something that communicates the purpose better.
There's no neat way on Packagist to just rename. The procedure is to start a new package and mark the previous one as abandoned.
I think what needs to be done:
Rename this repo on GitHub to brianhenryie/php-renamespacer
Rename the package name in composer.json
Create a new repo ~brianhenryie/strauss-renamed
The new repo is primarily just a composer.json with brianhenryie/php-renamespacer in its require
Point brianhenryie/strauss on Packagist to brianhenryie/strauss-renamed repo
Create a new package on Packagist for brianhenryie/php-renamespacer
Add a GitHub Actions workflow in brianhenryie/strauss-renamed that creates a new release every time brianhenryie/php-renamespacer is released*
Add a CLI output in brianhenryie/strauss-renamed to advise on using the new package name, and a tool to perform the change
I think this will mean existing users of brianhenryie/strauss will be pointed to brianhenryie/strauss-renamed and will continue to work for existing and future releases, while outputting a message advising to run a command to change the name. The * above is that maybe the the repo will need all existing releases in brianhenryie/strauss have a corresponding release in brianhenryie/strauss-renamed .
Not really no, that's way overcomplicated. Just do the first two steps, and then resubmit the repo url to get a second package on packagist with the new name. Then you can mark the old one as abandoned on packagist and point to new name.
I've never really liked the name and would prefer something that communicates the purpose better.
There's no neat way on Packagist to just rename. The procedure is to start a new package and mark the previous one as abandoned.
I think what needs to be done:
brianhenryie/php-renamespacer
composer.json
brianhenryie/strauss-renamed
composer.json
withbrianhenryie/php-renamespacer
in itsrequire
brianhenryie/strauss
on Packagist tobrianhenryie/strauss-renamed
repobrianhenryie/php-renamespacer
brianhenryie/strauss-renamed
that creates a new release every timebrianhenryie/php-renamespacer
is released*brianhenryie/strauss-renamed
to advise on using the new package name, and a tool to perform the changeI think this will mean existing users of
brianhenryie/strauss
will be pointed tobrianhenryie/strauss-renamed
and will continue to work for existing and future releases, while outputting a message advising to run a command to change the name. The*
above is that maybe the the repo will need all existing releases inbrianhenryie/strauss
have a corresponding release inbrianhenryie/strauss-renamed
.Good reading:
@Seldaek Does all that make sense?
The text was updated successfully, but these errors were encountered: