Pull requests don't pass

[yarax]

Guys, seems like new awesome bot doesn't pass new pull requests, because already existing links in README:
#156
https://travis-ci.org/chentsulin/awesome-graphql/builds/190590030
So as you see tests are failed because of

Issues :-(
> Links 
  1. [L124] 404 https://github.com/rmosolgo/graphql-relay-ruby  
  2. [L293] 301 https://github.com/kriasoft/graphql-starter-kit  → https://github.com/kriasoft/nodejs-api-starter 

not because of swagger2graphql itself

[pluma]

I've addressed the most recent batch of errors in #164

I guess #162 is a more permanent solution to this problem but would require running awesome bot manually every now and then to catch outdated URLs.

[yarax]

Can I help here with something?

[pluma]

FWIW the contributor badge just means I've had a PR merged. I'm not a maintainer.

That said, it's probably past the maintainer's bedtime right now: https://time.is/Taipei

So I guess just wait a day or so ;)

[pluma]

@yarax FYI #164 was merged and master is now green again (until the next URI falls out of date).

[yarax]

Tried again. Still fails because of other links :( #167

[m1guelpf]

I think you should really consider #162

[yarax]

@m1guelpf can you please explain what should I consider?
162 PR is about checking only changes.
I'm suggesting my changes and getting back error in another part of file:

Issues :-(
> Links 
  1. [L365]  http://swapi.graphene-python.org Connection reset by peer 

[pluma]

Awesome!

@stubailo Any chance of getting green PRs merged now?

[yarax]

Thank you @stubailo !