feat: remove upgrade python requirements #191
Merged
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
We enabled this workflow but there's no Python in the repository, so there's no point to run the workflow. * dkaplan1/feat-remove-Python-requirements-from-JS-only-repo
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #191 +/- ##
=======================================
Coverage 69.60% 69.60%
=======================================
Files 27 27
Lines 408 408
Branches 90 90
=======================================
Hits 284 284
Misses 123 123
Partials 1 1 ☔ View full report in Codecov by Sentry. |
jsnwesson
approved these changes
Oct 2, 2023
deborahgu
deleted the
dkaplan1/feat-remove-Python-requirements-from-JS-only-repo
branch
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.
We enabled this workflow but there's no Python in the repository, so there's no point to run the workflow.