Validate pull requests with Travis

[awesome-bot]

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

[stevemao]

Hi, I believe https://github.com/dkhamsing/frankenstein is more handy because it auto sends a PR when there is any url redirects. So I don't need to set up the CI. I have already received one #4.

[awesome-bot]

@stevemao the two tools are related but a bit different, one is to fix things one time.. the other is to periodically check if you have it part of a pull request but yeah it's up to you 😉

[stevemao]

Hm.. I just prefer not adding metadata files. It would be great if the bot can leave a comment on the PR or creating an issue if the url is wrong. So I prefer a web hook than integrating with CI.

[awesome-bot]

Thanks for the feedback

[awesome-bot]

@stevemao if you prefer not to add meta data to the repo, you can use awesome_bot with circle ci and configure it there https://circleci.com/

[stevemao]

Yup, I think that's a perfect use case :) thanks.

Sent from my iPhone

On 29 Apr 2016, at 5:05 AM, awesome-bot [email protected] wrote:

@stevemao if you prefer not to add meta data to the repo, you can use awesome_bot with circle ci and configure it there https://circleci.com/

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub