Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename composer vendor prefix #1

Open
chillu opened this issue Feb 27, 2013 · 0 comments
Open

Rename composer vendor prefix #1

chillu opened this issue Feb 27, 2013 · 0 comments

Comments

@chillu
Copy link

chillu commented Feb 27, 2013

Hello! First of all, thanks for getting on board with Composer with us, and registering your module on Packagist! We rely on early adopters like you to push adoption, and are thrilled to see such an enthusiastic uptake of Composer :)

We've noticed that you're using the "silverstripe" vendor prefix, which should only be used for modules maintained by the SilverStripe Ltd. organization (details). We'd like to ask you to change your vendor prefix accordingly by changing the name key in your composer.json. Usually using your github name is a good idea. The fact that this repo is a SilverStripe module is already contained in the "type": "silverstripe-module" metadata.

In order to ensure existing links to the module continue to work, please add a "replace" key to your composer.json:

"replace": {"<old-name>": "*"}

If you have created branches and releases containing a composer.json file,
it is recommended that you push the change there as well (and create new releases).
Once the name change is committed, force update the module on Packagist.

Note that the name change is only for Composer, you can call your github repository
however you like.

Thanks
Ingo Schommer, SilverStripe Core Developer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant