Skip to content
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

build: disables coverage threshold for new files #41

Merged
merged 1 commit into from
Feb 21, 2024

Conversation

tdstein
Copy link
Collaborator

@tdstein tdstein commented Feb 21, 2024

No description provided.

Copy link

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
473 425 90% 80% 🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: a666985 by action🐍

@tdstein tdstein merged commit 107433c into main Feb 21, 2024
7 checks passed
@tdstein tdstein deleted the tdstein/change-coverage-settings branch February 21, 2024 16:53
@@ -43,6 +43,4 @@ jobs:
with:
coverageFile: coverage.xml
thresholdAll: 0.8
thresholdNew: 0.9
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why, out of curiosity?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was causing CI to fail on files that were updated during refactoring. Similar to the behavior that drove the change to set thresholdAll: 0.8. I'd like to re-enable it soon once things have settled.

dbkegley pushed a commit that referenced this pull request Feb 21, 2024
* doc: put some words in README.md (#38)

* feat: adds passthrough methods for each HTTP request type (#25)

* feat: adds connect_version property to Client (#39)

* build: disables coverage threshold for new files (#41)

* ci: adds main.yaml (#42)

* ci: fixes main.yaml job name (#43)

---------

Co-authored-by: Neal Richardson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants