This repository has been archived by the owner on Jul 8, 2020. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #16
See pr here erezrokah/gatsby-netlify-cms-aws#10
I'm still missing the github status updates, but I'm assuming it is due to this:
![image](https://user-images.githubusercontent.com/26760571/60829574-db33b280-a1bd-11e9-984e-80f99eba7526.png)
(Still waiting for the bot response)
You can test it by installing directly from my branch:
yarn add --dev "https://github.com/erezrokah/lighthousebot#add_circle_ci_support"
Also I think there is a bug in the Travis support.
TRAVIS_PULL_REQUEST_SLUG
should beTRAVIS_REPO_SLUG
(https://docs.travis-ci.com/user/environment-variables/).I think in case of forks
TRAVIS_PULL_REQUEST_SLUG
will contain the information of the fork, where you actually want to update the current repo status (I'm not sure since I don't use Travis).