-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing github intergrations #100
Conversation
Codecov Report
@@ Coverage Diff @@
## master #100 +/- ##
=======================================
Coverage 91.01% 91.01%
=======================================
Files 14 14
Lines 534 534
=======================================
Hits 486 486
Misses 48 48 Continue to review full report at Codecov.
|
So..
...(no idea how to bring snyk back) but only the code-cov is able to report status to github? (Because I've installed the app into this repo?) |
It may be a dumb question (you'll notice I have plenty of those), but isn't that precisely the purpose of the github-bot ? The readme isn't that clear, but it seems to indicate it can be used to display travis reports. |
Progress: we need to use the github bot of the organization to post build status now, since we don't allow any third-party access to the nodejs organization except our own bots. Refs: nodejs/nodejs.org#355 Before I got the bot hooked into this repo we will need to go see the Travis & Appveyor status ourselves in https://travis-ci.org/nodejs/node-core-utils and https://ci.appveyor.com/project/joyeecheung/node-core-utils (yes it's under joyeecheung but it's actually triggered by activities in this repo because I've got the service hooks setup) EDIT: yes basically what #100 (comment) says lol |
PR opened in nodejs/github-bot#156 . To fix appveyor we need to implement a new script in the bot... |
Wasn't a dumb question after all then 😄 Awesome work! |
c661d76
to
0be4c5c
Compare
Uh, that's weird, the github bot deployed on my own server with my own token can update the status of this PR, but the github bot deployed in the foundation's server got 404 when it tries to |
9c45ae2
to
fa711ad
Compare
fa711ad
to
a2ed5f2
Compare
Ah, I think I've got this working! |
Yes, it's working properly now. Next step is to implement the appveyor couterpart |
This reverts commit 4566667.
I am going to close this and open another one when I start implementing appveyor scripts |
This PR is for testing how we can bring the CI integrations back without granting third-party access to those services..