-
Notifications
You must be signed in to change notification settings - Fork 459
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
Issue/592 #598
Issue/592 #598
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be also cool to integrate the respective badge in the README. :)
[![CI](https://github.com/barbushin/php-imap/actions/workflows/php.yml/badge.svg)](https://github.com/barbushin/php-imap/actions/workflows/php.yml)
running pinned version per barbushin#598 (comment) whilst also running against latest version as heads up for any potential issues
@Sebi94nbg should travis be dropped as part of this PR? |
If both are doing the same, I would say yes as we otherwise would only need to manage the same thing twice. |
The only issue at present is this PR isn't set up to generate coverage reports, I'll give the codeclimate action a go without using a hardcoded reporter ID. |
per 993b51b, travis has been dropped. |
Alright. Can I merge it now? Or are you still changing something on it? :D |
|
@barbushin can you please set the secret / environment variable in the repository settings? You're the only one, who has the permissions to do this. :) Otherwise we need to keep the secret in Git, what is not that beautiful. |
it's more a matter of making it easier to manage coverage in forks.
https://docs.codeclimate.com/docs/finding-your-test-coverage-token |
running pinned version per barbushin#598 (comment) whilst also running against latest version as heads up for any potential issues
dropping travis as discussed in barbushin#598 (comment)
I'll merge this now in order to fix the cs-fixer issues in the pipeline. |
running pinned version per #598 (comment) whilst also running against latest version as heads up for any potential issues
dropping travis as discussed in #598 (comment)
Travis CI integration has been removed/dropped in May 2021. See commit 993b51b.
re: #592
generating code coverage should be possible, although personally I switched our fork to codecov a while ago.