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

Initiated By: Stuart Herbert
Branch: feature/multiple-vagrantfiles
New: change default --target to be the new test environment

feature/multiple-vagrantfiles . 66da47...7aa491 . push triggered

  Data is cleaned up.
168:43
created
New: captured multiple-vagrantfiles details

feature/multiple-vagrantfiles . 9a609a...66da47 . push triggered

  Data is cleaned up.
120:54
created
Fix: move supporting files for CentOS6 into test env folder

feature/multiple-vagrantfiles . 57e0d3...9a609a . push triggered

  Data is cleaned up.
46:34
created
Fix: dsbuild files can now live with the test environment config file

feature/multiple-vagrantfiles . 0c06ec...57e0d3 . push triggered

  Data is cleaned up.
48:42
created
Fix: case-sensitive filesystems

feature/multiple-vagrantfiles . 0c06ec . push triggered

  Data is cleaned up.
07:04
created