-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add CI config for github actions #1786
Conversation
Codecov ReportBase: 93.76% // Head: 45.22% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main astronomer/astro-sdk#1786 +/- ##
===========================================
- Coverage 93.76% 45.22% -48.55%
===========================================
Files 93 25 -68
Lines 4937 973 -3964
Branches 486 90 -396
===========================================
- Hits 4629 440 -4189
- Misses 219 524 +305
+ Partials 89 9 -80 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
WDYT of labelling UTO PRs in a similar way to what we do with SQL CLI ones?
https://github.com/astronomer/astro-sdk/blob/main/.github/labeler.yml
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.
@utkarsharma2, as we discussed, I'm happy for us to have separate tickets/PRs for fixing the following checks:
- Fix type check
- Code coverage
I'm happy for the PR to be merged once Deep Source and the other checks pass.
Description
What is the current behavior?
Currently, we are not running any steps in CI for UTO
closes: #1724
What is the new behavior?
We added the GitHub actions config needed for CI to run Tests
Does this introduce a breaking change?
Nope
Checklist