Packagist github service hook? about ruckusing-migrations HOT 8 CLOSED

@ruckus could check this ?
Thanks

from ruckusing-migrations.

I'm really confused. I had setup the Packagist service hook in GitHub and just verified it again, the API token is correct and GitHub says its setup correctly.

But Packagist thinks its not setup correctly - check out the following screenshot, notice the top highlighted section.

Additionally, composer.json has a version of 0.1.1 but somehow Packagist thinks its 0.1.2 (the 2nd highlighted circle)...

Not sure whats happening..

from ruckusing-migrations.

I just tag 0.1.2 and update composer.json to 0.1.2, so seeing 0.1.2 is ok. but the github hook ... you can try again... :)
Thanks

from ruckusing-migrations.

I'm stumped. I've gone back to the service hook settings and verified them multiple times and clicked "Update" and "Test Hook" and all says its well.. but Packagist still says its not set for auto-update.

from ruckusing-migrations.

Finally got this resolved - had the wrong domain setting in the service hook.

from ruckusing-migrations.

Aha, could this be related to my issue with probably having a old version of ruckusing @ruckus ?
As in pull request #105

from ruckusing-migrations.

Yes maybe. Try updating.

On Jun 19, 2013, at 8:19 AM, Victor Bjelkholm [email protected] wrote:

Aha, could this be related to my issue with probably having a old version of ruckusing @ruckus ?

—
Reply to this email directly or view it on GitHub.

from ruckusing-migrations.

what did enter in the "domain" input ?

from ruckusing-migrations.