Register to Packagist

[franz-josef-kaiser]

I just got the following note in the CLI:

Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package manovotny/wptest could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> for more details.

Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Looking your user name up on Packagist revealed that the package isn't registered at all.

Steps to fix this and add autoupdating(!):

1. Register the repo on Packagist (big ass button named "Submit package")
2. Go to your "Settings > Hooks" page here on GitHub: Link and search for "Packagist", then enter/confirm to create
3. Add your username and password and save it
4. Copy your Token from Packagist to the repo
5. Reopen the "Packagist" hook by clicking the link
6. Hit the "Test" button on the upper right to send a ping for autoupdates

Thanks.

[Viper007Bond]

Due to the lack of action, I've just gone ahead and done it myself:

https://packagist.org/packages/poststatus/wptest

Obviously I can't set up the GitHub hooks so that it auto-updates on Packagist but since there hasn't been any changes to wptest in a long time, it's not the end of the world.

@poststatus I will happily hand over control on Packagist if you guys decide you ever want to manage it yourself. The code all comes from your repo though so I'm not really in control of anything other than hitting update.