Remote Git Repository
For stack-based processes, OrgFlow uses a Git repository to maintain a record of your Salesforce metadata and its history.
Every Stack needs to be linked to a single remote Git repository. The location of this repository is set when you run the stack:create command.
Which Git services are supported by OrgFlow?
There are many Git services available, and OrgFlow supports every single one. The only requirement is that the OrgFlow process is able to connect to the remote repository location (e.g. there are no firewall or network restrictions that would prevent the OrgFlow process from communicating with the remote Git repository).
When we say any, we mean any: GitHub, Azure DevOps, GitLab, Bitbucket, AWS CodeCommit, or even an internal Git server on your corporate network.
OrgFlow processes all of your Salesforce metadata locally on the machine that is running the OrgFlow process. This means that if your remote Git repository is protected by firewall rules then you do not need to alter these rules to allow for an externally hosted process to be able to access the remote Git repository.
Some Git services allow you to create a repository that is visible to the public. Your Salesforce metadata will be committed to this repository, so be careful not to accidentally use a public repository if you are not comfortable making your Salesforce metadata visible to the public.