💚 🔧 Missing GitHub Actions CI Configuration for Testing and Automatic Publishing

[MEHRSHAD-MIRSHEKARY]

Description:

The package lacks a GitHub Actions CI configuration to automate testing and publishing. Without a CI setup, there’s no automated way to ensure that the code passes all tests before merging and that the package is automatically published to a package registry (e.g., PyPI) when a new version is released. This manual process increases the risk of errors, delays in releases, and untested code being merged.

Problems Identified:

1. No Automated Testing:

   • There is no GitHub Actions workflow to automatically run tests on each push or pull request. This leads to potential issues such as:
     • Code that doesn’t pass tests being merged into the main branch.
     • Manual effort required to ensure tests are run, increasing the risk of oversight.

2. No Automatic Publishing:

   • Without a CI pipeline for publishing, each release must be manually handled, which can lead to:
     • Missed steps during publishing (e.g., version bump, building the package, publishing to PyPI).
     • Delayed or inconsistent release schedules.

3. Lack of Consistency:

   • Manual processes for testing and publishing can lead to inconsistent environments, especially between local machines and CI. This increases the likelihood of "works on my machine" problems.

4. No Version Control on Releases:

   • The lack of automated publishing means there's no consistent control over versioning and releases. Semantic versioning may be skipped or mishandled.