I am reading this page to get a grasp on a good workflow for Umbraco Cloud: https://docs.umbraco.com/umbraco-cloud/getting-started/git-repository-in-a-cloud-project My takeaway is to have two repos: 1. Your own git repo to have your actual code changes in. I assume for template files, custom C# files for backend etc. 2. A cloned repo of the dev environment from Umbraco Cloud. When you make actual changes to your code you do it in your own repo, I assume. But then what? Copy paste changed files to repo two and commit? It sounds very tedious. What am I missing here?

IMO there are no amazing solutions right now with the way Cloud requires a backing git repo and the fact that they commit auto upgrades directly to it. However, the way we do it is that repo is the same, so when you work locally you have 2 git remotes, our Azure DevOps repo where we do PRs, etc, and the Umbraco Cloud repo that we can pull autoupgrades from and push to in order to deploy. So there is no need to copy files over, but there is a need to fetch multiple remotes and merge branches together before pushing them to those remotes to ensure everything is aligned and up to date. Cloud has a CI/CD implementation where you can automate the deployments from your own repo which could make parts of this easier as well.

Aha ok, thank you. It seemed like you were supposed to use two different repos for two different sets of files.

It used to be that way with the old .NET Framework sites, but is no longer required 🙂 don't know if the documentation makes that clear