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
[ci] Added python 3.9 #12 #13
Conversation
hey @codesankalp, please review this. |
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.
Looks good, I don't think any further change is required here, thanks @harsh-9in !
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.
Argh, I can't merge!
Can you please remove .travis.yml
file? We'll be able to merge it then, please ensure all the tests from .travis are moved to github action.
Reason: We used travis-ci in the past but that's not working very well so Gagan helped us move to GitHub actions which is what we are using for our CI needs now! 😄
@atb00ker I can't find any |
@devkapilbansal and @atb00ker, I think status checks are defined in branch protection rules: https://travis-ci.community/t/known-issue-travis-ci-reports-expected-waiting-for-status-to-be-reported-on-the-github-status-api-but-the-status-never-arrives/1154 |
I removed the leftover travis configuration in the branch protection rule, are you allowed to merge now? |
That worked, thanks! 😄 |
Added python 3.9 in ci
fixed: #12