Closed GabLeRoux closed 2 months ago
It's a very great suggestion from @GabLeRoux. I can help you with this, by adding the necessary actions. Its also a good starter for me to start contributing to this cool project @Flexonze.
Most of the work is already done in #1 for this current issue, but here are some other ideas that will also improve this project:
release/x.x.x
:
generate_release_notes
set to true, it works very well)coveralls
https://github.com/marocchino/sticky-pull-request-comment🙏
Hey @hammadarshad1! @GabLeRoux has already taken care of it, but your contribution is more than welcome! I've added a bunch of issues that would be useful if you want to take a look, or feel free to open your own issues. :smile:
Hey @hammadarshad1! @GabLeRoux has already taken care of it, but your contribution is more than welcome! I've added a bunch of issues that would be useful if you want to take a look, or feel free to open your own issues. 😄
I'll quickly look for new issues. I would definitely love to contribute. Thanks
To improve code quality and catch issues early, we should add the following to the GitHub Actions workflow:
ruff
to enforce consistent code style and catch linting errors.Goal: Update the GitHub Actions configuration to run both tests and
ruff
on each CI run.