#2613 [Housekeeping] Create github workflows in Cookie Cutter template Issue created by EngHabu Describe the issue Cookie cutter template: https://github.com/flyteorg/flytekit-python-template Comes with a Dockerfile, scripts and configs but one thing it lacks is demonstrating best practices around iteration/development (CI/CD) as described here. I think we should add github workflows as follows: 1. PullRequest: a. Build Dockerfile b. Start flytectl demo cluster c. Register against it 2. Promote to Domain: a. Take the desired domain as an input (e.g. Staging/Production), a commit sha/tag, an optional URL of the org b. Build Dockerfile c. Start flytectl demo cluster (if org url is not provided) d. Register against it We should add instructions to advise people to: 1. Configure the Build Dockerfile step to push to their favorite Registry 2. Update the workflow code to default to their org if that's provided (or maybe make that an optional cookie cutter input?) What if we do not do this? Need to explain how users can build this using flyte's provided actions/tools Related component(s) No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte