-
Notifications
You must be signed in to change notification settings - Fork 232
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
Implementing Github Actions #468
Conversation
Thanks for the PR! It'd be nice to get confirmation from someone else who has been waiting on this that everything works for them before I merge and make a release. |
@ksuther I can confirm that everything works, our company is using Github actions and slather. thanks @martin-key for implementing these changes! |
@ksuther I will do a few minor amendments and will post here when it is ready for merging. |
…appears in coveralls
488ad76
to
aab480b
Compare
Ok, all the commits are correctly squashed and also I have improved the documentation so the correct branch appears in coveralls. |
Great, merging it and making a release. Thanks to everyone who helped on this :) |
One of the new tests failed in Travis. Not sure why it didn't show up in the PR though. Is this passing on your end? https://travis-ci.org/github/SlatherOrg/slather/builds/747088844
|
LGTM from coveralls. |
Implementing Github Actions
Summary
As I needed the Github actions working for slather and coveralls I have used #459 as a base to start debugging and to find the problem. I have sent an email to coveralls support and they have answered that for github actions they are not using the coveralls repo secret, but they are using the
GITHUB_TOKEN
env secret from github actions. I have implemented that change and also I have added some more useful env variables for the report generation.Result
As a result the reports are working correctly using slather with github actions and coveralls.
References that I have used for the development:
Additional info