Closed luisrgpt closed 3 years ago
It seems a good idea! What do you need for that?
To be honest, this is my first time using GitHub Actions. However, as far as I can see, it is pretty much straightforward. I'll first create a workflow so that the source code is tested and inspected every time a push or a pull request is made. Then we can see if it is doable to publish our code into PyPI.
This repository is now, on its own, capable of testing/evaluating its code and generating packages delivered in the testing environment of PyPI. I've not yet written the workflow that GitHub Actions will use to publish our releases into the real PyPI since we are going to validate what we are going to publish first.
Also, I haven't found a way, for now, to automatically increment the version of our packages at GitHub Actions. We should also address this issue before publishing releases.
@luisrgpt could you please provide me the proper link for the PyPI published source? Thank you.
@FMCalisto We haven't one yet. However, you can see a POC in the https://test.pypi.org/project/mi-downloader/.
Now that we have some unit tests, and our code refactored, we could keep passing our tests and keep our code clean. We could even further expand our test suite and ensure our code is cleaner than ever, and monitor our progress in those fields. For most of that to happen automatically, I believe we could apply CI/CD into our software.
Since we are storing this repository at GitHub, why not using GitHub Actions? It's free for FOSS, and does not require additional third-party tools.