Add github flow for ci #1044
Merged
Add github flow for ci #1044
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1044 +/- ##
=========================================
Coverage ? 75.22%
=========================================
Files ? 73
Lines ? 8203
Branches ? 726
=========================================
Hits ? 6171
Misses ? 1857
Partials ? 175 ☔ View full report in Codecov by Sentry. |
|
This got stuck waiting for the pipeline checks that were not anymore part of it, even after removing those specific checks from the branch protection requirements. Removing the branch protection temporarily fixed this :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR converts away from azure pipelines to github actions which simplifies the setup & make coverage working again.
When that works, it will be much simpler to add a workflow for doing releases (incl. changelog generation, tagging, and publishing to pypi), hopefully. The aim is to make it releasing not a chore.