search

elixir-cloud-aai / TESK

GA4GH Task Execution Service Root Project + Deployment scripts on Kubernetes
https://tesk.readthedocs.io
Apache License 2.0
39 stars 29 forks source link

build: clean up deps #180

Closed JaeAeich closed 4 months ago

JaeAeich commented 4 months ago

Description

Useless dependency group dev, this would just make it harder to maintain versions.

Note: Removed k8s from test deps group, it should be obv that to test, tesk should be installed :)

codecov[bot] commented 4 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.21%. Comparing base (cabf21c) to head (767f613).

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #180 +/- ## ======================================= Coverage 98.21% 98.21% ======================================= Files 8 8 Lines 559 559 ======================================= Hits 549 549 Misses 10 10 ``` | [Flag](https://app.codecov.io/gh/elixir-cloud-aai/TESK/pull/180/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=elixir-cloud-aai) | Coverage Δ | | |---|---|---| | [test_unit](https://app.codecov.io/gh/elixir-cloud-aai/TESK/pull/180/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=elixir-cloud-aai) | `98.21% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=elixir-cloud-aai#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

uniqueg commented 4 months ago

Also please note that fix, feat, refactor, perf and style are only for cases where the predominant changes are in the package code. ci, docs and tests are for predominant changes in the .github/workflows, docs and tests directories, respectively, even if they are bug-, performance- or style-related. Changes to dependencies and the build system are build. chore we use for repository housekeeping things like adding licenses or Git ignore etc. although it's a little bit ill-defined (some people stopped using it altogether).