Question on Travis CI and project scope about webhook HOT 4 CLOSED

Totally agree with you. I think the best solution would be to create a webhook-contrib repository where developers could contribute their webhook-oriented stuff that others might find useful, ranging from build spec files to hooks.json management tools. This repo should only contain the webhook source code...

Edit: I have created http://github.com/adnanh/webhook-contrib, we should migrate and organize all this stuff inside it, and then create a PR to remove it from this repo.

from webhook.

More than fine by me.
On 5 Nov 2015 8:11 a.m., "Adnan Hajdarević" [email protected]
wrote:

Totally agree with you. I think the best solution would be to create a
webhook-contrib repository where developers could contribute their
webhook-oriented stuff that others might find useful, ranging from build
spec files to hooks.json management tools. This repo should only contain
the webhook source code...

—
Reply to this email directly or view it on GitHub
#50 (comment).

from webhook.

👍

from webhook.

I've simply moved files to webhook-contrib in their separate folders. They probably need an adjustment now, since they are not in the same repo as the source code. @timhughes @moorereason @almir

from webhook.