Open null9beta opened 6 years ago
@null9beta I'll try to migrate it ASAP, thx for the reminder ;)
@mavimo actually there is no action needed from your side at the moment, but definitely thanks for picking that up so quickly, and thanks also for contributing here 👍 . I think even only we as the repo owner can even manage those settings. I actually just wanted to let you guys now that i will take care of changing from the services to github apps or webhooks (depending what they will offer)
I added the TravisCI github app already, BUT the migration is not available yet as there new website states. So i am waiting until that migration is available, see the screenshot
as i could not found anything regarding packagist, so i wrote them an email. This is the answer
We don't have an app yet, please use the old school way for now, we will inform user when we are ready to migrate. Best, Jordi
cheers
Can you please check whether the Packagist integration is working correctly? Since the end of January Travis CI shut down the GitHub services and you have to migrate to web hooks (https://packagist.org/about#how-to-update-packages). The biggest problem right now is that no new releases will be published and even the branches are not updated to the latest commit, so you always download an older commit if you point your composer.json
to the branch
@ste93cry looks like beat me to setting up a webhook, I'm guessing @mavimo :-)
@mickadoo at the end of January GitHub has disabled the legacy integration, so the user that publish the package on packagist should switch config to GitHub Apps. Looking the suggestion from seldaek in https://twitter.com/seldaek/status/1083667408479576065 seems that the only action needed is that one of the maintainer should login on Packagist and switch integration (should not be a long process).
I'm not a maintainer and can't procede in it, but if there is something that I can do to help let me know!
@mickadoo @null9beta your support should be very appreciated 😃
Thx for your time!
PS: maybe the message from @ste93cry should sound a bit rude, but I'm pretty sure is not in his intention beat anyone ☮️
Sorry if my message seemed rude, it wasn’t my intention at all. I just asked to check the integration with Packagist because at the moment it’s not working correctly. Should you feel my message was rude, please forgive me.
@ste93cry don't worry, I didn't think you were rude at all! :smiley:
@mavimo I had a look at the latest information on https://packagist.org/about - I don't think it has a Github App available yet and webhooks should do the job. There was a webhook there already, not sure who created it, but I replaced it with the hook as described on the packagist docs. It reported a successful response so hopefully it's doing its job now. If not just let me know :-)
@mavimo @mickadoo
first of all, as there seems to be no feature anymore that allows me to send messages to collaborators and members i am just using an issue for that :)
soon the service integrations setup for this repo (travis, packagist and code climate) will stop working, please see this article, it contains the deadlines. [https://developer.github.com/v3/guides/replacing-github-services/]()
I already added the travis github app, because i needed it for one of our open source repos.
Travis also changed the .tld, .org is used for the old services, .com is used for the github app. services: [https://travis-ci.org/profile/loopline-systems]() github app: [https://travis-ci.com/profile/loopline-systems]()
your github logins should just work fine on the .com travis platform.
I saw that there is a migration feature to get all the builds migrated from the services platform into the github app platform, but it`s not showing so far. So i need to investigate on that.
about the other to service, codeclimate and packgist, i will start checking about migrating to github apps soon, and let you know about the staus here