List view
Ideally if any user is making a fork or direct committing to cookiecutter-robust-python, then the process of updating demos, creating the PR's, and merging upon action success should all be an automatic process happening in the background. It's incredibly important that this process occurs within the owner of the fork or branch's repos as to help spread out CICD usage until this project is funded / can support its own costs.
No due dateGet all locally operating CI for Maturin based projects working. This goal is mostly targeting the initial local development experience.
No due date