GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.

Inspections

Run tests into travis containers

master . #249 . pull request triggered

  No notable changes.
02:12
created
Run tests into travis containers

master . #249 . pull request triggered

  No notable changes.
02:27
created
Run tests into travis containers

master . #249 . pull request triggered

  No notable changes.
02:25
created
Run tests into travis containers

master . #249 . pull request triggered

  No notable changes.
02:25
created
Run tests into travis containers

master . #249 . pull request triggered

  No notable changes.
02:27
created
Run tests into travis containers

master . #249 . pull request triggered

  No notable changes.
02:57
created
Run tests into travis containers

master . #249 . pull request triggered

  No notable changes.
02:39
created
JMS serializer in 1.7.0 will revert a BC break introduced in 1.6.1

master . #247 . pull request triggered

  Data is cleaned up.
53s
created
Max depth issues when used with "embedded" relations

master . #246 . pull request triggered

  11 new issues, 2 fixed issues found.
02:26
created
Max depth issues when used with "embedded" relations

master . #246 . pull request triggered

  11 new issues, 2 fixed issues found.
02:16
created
Max depth issues when used with "embedded" relations

master . #246 . pull request triggered

  11 new issues, 2 fixed issues found.
04:21
created
Max depth issues when used with "embedded" relations

master . #246 . pull request triggered

  11 new issues, 2 fixed issues found.
04:23
created