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

feat: hydroweb_next as new provider #711

Merged
merged 1 commit into from
Apr 14, 2023
Merged

feat: hydroweb_next as new provider #711

merged 1 commit into from
Apr 14, 2023

Conversation

sbrunato
Copy link
Collaborator

Closes #686

Adds hydroweb_next as new provider.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 14, 2023

Test Results

    2 files  ±0      2 suites  ±0   2m 17s ⏱️ -1s
379 tests ±0  376 ✔️ ±0  3 💤 ±0  0 ±0 
758 runs  ±0  752 ✔️ ±0  6 💤 ±0  0 ±0 

Results for commit b61f478. ± Comparison against base commit 3018325.

♻️ This comment has been updated with latest results.

@github-actions
Copy link
Contributor

File Coverage
All files 89%
tests/units/test_core.py 98%

File Coverage
All files 88%
tests/units/test_core.py 98%
tests/units/test_core.py 98%

Minimum allowed coverage is 70%

Generated by 🐒 cobertura-action against b61f478

@sbrunato sbrunato merged commit ba515f3 into develop Apr 14, 2023
@sbrunato sbrunato deleted the hydroweb-next branch April 14, 2023 13:14
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.

Add hydroweb_next as new provider
1 participant