This repository has been archived by the owner on Jul 8, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 127
Run on non-PR's #34
Comments
What's the use case you have in mind?
…On Thu, Jun 7, 2018, 10:27 PM kontrollanten ***@***.***> wrote:
Thanks for a great package! Would it be possible to allow this to be ran
on non-pull request events in Travis? Then it could fetch PR number, etc
from the GH API; like
https://api.github.com/repos/ebidel/lighthouse-ci/pulls
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#34>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOigIrv1gIdOJBM_jpKtc85ITl7kcStks5t6gtZgaJpZM4Ufg2s>
.
|
I'm triggering my Travis build with the API after I've deployed my PR preview |
I made a fork to do a poc; kontrollanten@b6ad518 Please let me know if you want me to do a PR |
Ah neat. Yea, a PR would be great. Changes are pretty minimal and I like the idea of making this more configurable :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thanks for a great package! In my case my site is not deployed through Travis, instead my deploy service (Netlify) triggers a web hook to run e2e and lighthouse after deploy.
Would it be possible to allow this to be ran on non-pull request events in Travis? Then it could fetch PR number, etc from the GH API; like https://api.github.com/repos/ebidel/lighthouse-ci/pulls
The text was updated successfully, but these errors were encountered: