brey / pyPoseidon

Framework for hydrodynamic simulations of geoflows
https://pyposeidon.readthedocs.io/
European Union Public License 1.2
7 stars 8 forks source link

Remove azure-pipelines #35

Closed pmav99 closed 3 years ago

pmav99 commented 3 years ago

As soon as we are satisfied with the github actions setup, we could consider removing the azure pipelines from the project

ideally, we should keep both so that we are not coupled to a specific service, but we probably lack the resources to maintain both at the same time.

brey commented 3 years ago

I agree. Github actions are more integrated and they are the same backend anyway.

brey commented 3 years ago

We need to name appropriately the yaml files because they name the badges on README.

brey commented 3 years ago

Also... do you know how we can add a badge for coverage? It came bundled with azure but maybe there is another way..

pmav99 commented 3 years ago

We need to name appropriately the yaml files because they name the badges on README.

Rename as you see fit :)

Also... do you know how we can add a badge for coverage? It came bundled with azure but maybe there is another way..

I haven't set it up. Something like this will probably do

https://github.com/marketplace/actions/coveralls-python

brey commented 3 years ago

We need to name appropriately the yaml files because they name the badges on README.

Rename as you see fit :)

Is the 'pip' name consistent? I assume this is the CI for the pip installation.

Also... do you know how we can add a badge for coverage? It came bundled with azure but maybe there is another way..

I haven't set it up. Something like this will probably do

https://github.com/marketplace/actions/coveralls-python

Thanks

brey commented 3 years ago

done with 1bb786c