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.
List view
0 issues of 0 selected
There are no open issues in this milestone
Add issues to milestones to help organize your work for a particular release or project. Find and add issues with no milestones in this repo.